Updates:
Status: Fixed
Comment #2 on issue 1163 by [email protected]: Worse two-node cluster
failovers on 2.12
https://code.google.com/p/ganeti/issues/detail?id=1163
commit bc06ac2370a14d934e5b2164f59e4ca606a8a8e4
Author: Klaus Aehlig <[email protected]>
Date: Fri Jan 8 14:51:20 2016 +0100
Document healthy-majority restriction on master-failover
The previous patch introduced a behavioral change for master-failover:
it is rejected unless a majority of nodes is healthy or the --no-voting
option is given. (While we in general do not change behavior on a stable
branch, rejecting an operation that can be retried with different
command-line
options is better than breaking the cluster completely.) Document this.
Signed-off-by: Klaus Aehlig <[email protected]>
Reviewed-by: Helga Velroyen <[email protected]>
commit 511552616402b2e341201ec83ea65af02f878ad9
Author: Klaus Aehlig <[email protected]>
Date: Fri Jan 8 11:37:17 2016 +0100
Check for healthy majority on master failover with voting
The normal procedure for a master failover is that, after telling
each node the new master, the daemons on the new master node are
started the standard way, i.e., with voting. This, however, requires
that a majority of nodes is still healthy; otherwise, the failover
will result in the daemons not starting and thus a broken cluster.
Therefore, reject master failovers with voting, unless we can verify
that a majority of nodes is still responding.
Signed-off-by: Klaus Aehlig <[email protected]>
Reviewed-by: Helga Velroyen <[email protected]>
commit d2dc0cb1492a9872c19544d778a3ab814ea2d491
Author: Klaus Aehlig <[email protected]>
Date: Fri Jan 8 12:26:57 2016 +0100
Add a predicate testing that a majority of nodes is healthy
For standard master failover (with voting), it is necessary
that the majority of nodes is still reachable and can answer
questions about which node is master. Add a predicate verifying
that this is still true.
Signed-off-by: Klaus Aehlig <[email protected]>
Reviewed-by: Helga Velroyen <[email protected]>
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
