[sheepdog-users] Cluster recover after loosing 2 devices

[Andrew J. Hobbs]

I'd agree with that.

n 06/18/2014 12:55 PM, Valerio Pachera wrote:



2014-06-18 17:49 GMT+02:00 Andrew J. Hobbs <ajhobbs at desu.edu<mailto:ajhobbs at desu.edu>>:
Perhaps I'm misunderstanding your scenario.

You had a cluster running sheepdog md using -c 2.  A device failure on one node triggered a node level recovery of lost blocks.  However, your cluster was over-committed, resulting in the node level recovery overflowing the available space left on the node.  During this process, another node failed in similar fashion.  Sheepdog was unable to recover, but you were able to manually recover the vdis, however their content was corrupt?

Is that a valid summary of what happened in your situation?

Exactly :-)

If so, then I'd argue the corruption stems from not properly dealing with the over-committed state, which is where the corruption likely originated from.  So reasonable to say that perhaps the proper solution would be during node recovery, determine if the committed space on that node will exceed the available space left on devices, and only then trigger a cluster re-weight procedure, which is quite expensive.

Yes, expensive but better than disk full and the consequences.

Note there's still a window for data loss as if a missing piece is on another node's device which has also coincidentally failed, then there's no location to pull that block from and the cluster should probably halt.

Agreed!
The loss of a single disk is as dangerous as the loss of a whole node.


There's never a way to make this sort of thing invulnerable.  There's always some corner case where data loss or corruption is possible.

Yep, but I think in my case, if the cluster was going to halt when the second disk broke down, I'm pretty sure the content of the vdi was not going to be corrupted.
So I think we can improve this.

It's matter of halting the cluster for manual intervention in extreme cases it can't handle itself.




-------------- next part --------------
A non-text attachment was scrubbed...
Name: ajhobbs.vcf
Type: text/x-vcard
Size: 353 bytes
Desc: ajhobbs.vcf
URL: <http://lists.wpkg.org/pipermail/sheepdog-users/attachments/20140618/ef7f9697/attachment-0005.vcf>