If the watcher is disabled at cluster level (via the
**gnt-cluster watcher pause** command), it will exit without doing
-anything. The cluster-level pause can be overriden via the
+anything. The cluster-level pause can be overridden via the
``--ignore-pause`` option, for example if during a maintenance the
watcher needs to be disabled in general, but the administrator
wants to run it just once.
FILES
-----
-The command has a state file located at
-``@LOCALSTATEDIR@/lib/ganeti/watcher.data`` (only used on the master)
-and a log file at ``@LOCALSTATEDIR@/log/ganeti/watcher.log``. Removal
-of either file will not affect correct operation; the removal of the
-state file will just cause the restart counters for the instances to
-reset to zero.
+The command has a set of state files (one per group) located at
+``@LOCALSTATEDIR@/lib/ganeti/watcher.GROUP-UUID.data`` (only used on the
+master) and a log file at
+``@LOCALSTATEDIR@/log/ganeti/watcher.log``. Removal of either file(s)
+will not affect correct operation; the removal of the state file will
+just cause the restart counters for the instances to reset to zero, and
+mark nodes as freshly rebooted (so for example DRBD minors will be
+re-activated).
+
+In some cases, it's even desirable to reset the watcher state, for
+example after maintenance actions, or when you want to simulate the
+reboot of all nodes, so in this case, you can remove all state files:
+
+.. code-block:: bash
+
+ rm -f @LOCALSTATEDIR@/lib/ganeti/watcher.*.data
+ rm -f @LOCALSTATEDIR@/lib/ganeti/watcher.*.instance-status
+ rm -f @LOCALSTATEDIR@/lib/ganeti/instance-status
+
+And then re-run the watcher.
.. vim: set textwidth=72 :
.. Local Variables: