Revision 8e2524c3 man/gnt-cluster.sgml
b/man/gnt-cluster.sgml | ||
---|---|---|
442 | 442 |
|
443 | 443 |
<cmdsynopsis> |
444 | 444 |
<command>masterfailover</command> |
445 |
<arg>--no-voting</arg> |
|
445 | 446 |
</cmdsynopsis> |
446 | 447 |
|
447 | 448 |
<para> |
448 | 449 |
Failover the master role to the current node. |
449 | 450 |
</para> |
451 |
|
|
452 |
<para> |
|
453 |
The <option>--no-voting</option> option skips the remote node agreement |
|
454 |
checks. This is dangerous, but necessary in some cases (for example |
|
455 |
failing over the master role in a 2 node cluster with the original master |
|
456 |
down). If the original master then comes up, it won't be able to start |
|
457 |
its master daemon because it won't have enough votes, but so won't the |
|
458 |
new master, if the master daemon ever needs a restart. You can pass |
|
459 |
--no-voting to ganeti-masterd on the new master to solve this problem, |
|
460 |
and gnt-cluster redist-conf to make sure the cluster is consistent again. |
|
461 |
</para> |
|
462 |
|
|
463 |
<para> |
|
464 |
In version 2.0.X ganeti-masterd will not be able to start if |
|
465 |
masterfailover is called with the --no-voting option (which, again, |
|
466 |
should only be used on 2 nodes clusters with the former master being |
|
467 |
down). In that case just start it manually passing --no-voting to it |
|
468 |
as well, until you have restored cluster redundancy. |
|
469 |
</para> |
|
470 |
|
|
450 | 471 |
</refsect2> |
451 | 472 |
|
452 | 473 |
<refsect2> |
Also available in: Unified diff