Create a new --no-voting option for masterfailover

[ganeti-local] / man / gnt-cluster.sgml

diff --git a/man/gnt-cluster.sgml b/man/gnt-cluster.sgml
index e3fecbf..98ec7db 100644 (file)
--- a/man/gnt-cluster.sgml
+++ b/man/gnt-cluster.sgml
@@ -442,11 +442,32 @@
 
       <cmdsynopsis>
         <command>masterfailover</command>
+        <arg>--no-voting</arg>
       </cmdsynopsis>
 
       <para>
         Failover the master role to the current node.
       </para>
+
+      <para>
+        The <option>--no-voting</option> option skips the remote node agreement
+        checks. This is dangerous, but necessary in some cases (for example
+        failing over the master role in a 2 node cluster with the original master
+        down). If the original master then comes up, it won't be able to start
+        its master daemon because it won't have enough votes, but so won't the
+        new master, if the master daemon ever needs a restart. You can pass
+        --no-voting to ganeti-masterd on the new master to solve this problem,
+        and gnt-cluster redist-conf to make sure the cluster is consistent again.
+      </para>
+
+      <para>
+        In version 2.0.X ganeti-masterd will not be able to start if
+        masterfailover is called with the --no-voting option (which, again,
+        should only be used on 2 nodes clusters with the former master being
+        down). In that case just start it manually passing --no-voting to it
+        as well, until you have restored cluster redundancy.
+      </para>
+
     </refsect2>
 
     <refsect2>