26.01.2012 17:38, David Teigland wrote: > On Thu, Jan 26, 2012 at 03:15:40PM +0300, Vladislav Bogdanov wrote: >> Imagine (this case is a little bit hypothetical, but anyways): >> * You have cluster with 8 active nodes, and you (for some historical >> reasons or due to admin fault/laziness) have expected_votes set to 3 >> (ok, you had 3-node cluster not so long ago, but added more nodes >> because of growing load). >> * Cluster splits 5+3 due to loss of communication between switches (or >> switch-stacks). >> * 3 nodes are fenced. >> * Partition with majority continues operation. >> * 3 fenced nodes boot back, and form *quorate* partition because they >> have expected_votes set to 3 > > At this point, the fencing system on the 3 nodes should do startup fencing > of everyone in the quorate partition (see fenced man page under Domain > startup for explanation of startup fencing.) That's not nice behavior, > and a correct expected_votes would prevent it. But it's not as bad as > corruption. David, please see the message I sent to list several minutes ago. I describe a way to avoid startup fencing in the scenario above there. Best, Vladislav _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
