summaryrefslogtreecommitdiff
path: root/ctdb/doc
diff options
context:
space:
mode:
authorMartin Schwenke <martin@meltin.net>2013-06-21 14:32:50 +1000
committerAmitay Isaacs <amitay@gmail.com>2013-06-22 15:54:19 +1000
commit017b966669a622a9cceb3b7183304b93be02f48b (patch)
tree2f80bf2a50a48240ec21b13395328d6532d69609 /ctdb/doc
parent51150c772732846975ea9aa67107914c9cd6ce5f (diff)
downloadsamba-017b966669a622a9cceb3b7183304b93be02f48b.tar.gz
doc: Add nodestatus command to the ctdb manpage
Signed-off-by: Martin Schwenke <martin@meltin.net> (This used to be ctdb commit 4369c8e6ead9062ef7855ada375df74262acf925)
Diffstat (limited to 'ctdb/doc')
-rw-r--r--ctdb/doc/ctdb.1.xml65
1 files changed, 65 insertions, 0 deletions
diff --git a/ctdb/doc/ctdb.1.xml b/ctdb/doc/ctdb.1.xml
index ce83a3efa0b..887f92d3a36 100644
--- a/ctdb/doc/ctdb.1.xml
+++ b/ctdb/doc/ctdb.1.xml
@@ -324,6 +324,71 @@ Recovery master:0
</screen>
</refsect2>
+ <refsect2><title>nodestatus [&lt;nodespec&gt;]</title>
+ <para>
+ This command is similar to the <command>status</command>
+ command. It displays the "node status" subset of output. The
+ main differences are:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ The exit code is the bitwise-OR of the flags for each
+ specified node, while <command>ctdb status</command> exits
+ with 0 if it was able to retrieve status for all nodes.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>ctdb status</command> provides status information
+ for all nodes. <command>ctdb nodestatus</command>
+ defaults to providing status for only the current node.
+ If &lt;nodespec&gt; is provided then status is given for
+ the indicated node(s).
+ </para>
+
+ <para>
+ By default, <command>ctdb nodestatus</command> gathers
+ status from the local node. However, if invoked with "-n
+ all" (or similar) then status is gathered from the given
+ node(s). In particular <command>ctdb nodestatus
+ all</command> and <command>ctdb nodestatus -n
+ all</command> will produce different output. It is
+ possible to provide 2 different nodespecs (with and
+ without "-n") but the output is usually confusing!
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ A common invocation in scripts is <command>ctdb nodestatus
+ all</command> to check whether all nodes in a cluster are
+ healthy.
+ </para>
+
+ <para>
+ Example: ctdb nodestatus
+ </para>
+ <para>Example output:</para>
+ <screen format="linespecific">
+# ctdb nodestatus
+pnn:0 10.0.0.30 OK (THIS NODE)
+ </screen>
+
+ <para>
+ Example: ctdb nodestatus all
+ </para>
+ <para>Example output:</para>
+ <screen format="linespecific">
+# ctdb nodestatus all
+Number of nodes:2
+pnn:0 10.0.0.30 OK (THIS NODE)
+pnn:1 10.0.0.31 OK
+ </screen>
+ </refsect2>
+
<refsect2><title>recmaster</title>
<para>
This command shows the pnn of the node which is currently the recmaster.