[SCM] CTDB repository - branch master updated -
563cdf2bd9cca358d234c797d8e1d9c8838c6ca6
Ronnie Sahlberg
sahlberg at samba.org
Thu Jul 10 02:55:41 GMT 2008
The branch, master has been updated
via 563cdf2bd9cca358d234c797d8e1d9c8838c6ca6 (commit)
from b2ccb891b81b041e2186e038b67bb4354b7892aa (commit)
http://gitweb.samba.org/?p=sahlberg/ctdb.git;a=shortlog;h=master
- Log -----------------------------------------------------------------
commit 563cdf2bd9cca358d234c797d8e1d9c8838c6ca6
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date: Thu Jul 10 12:50:16 2008 +1000
add documentation for both LVS:single-ip and CAPABILITIES:wan-accelerator
-----------------------------------------------------------------------
Summary of changes:
doc/ctdb.1 | 45 ++++++++++++++-
doc/ctdb.1.html | 132 +++++++++++++++++++++++++++++--------------
doc/ctdb.1.xml | 78 ++++++++++++++++++++++++++
doc/ctdbd.1 | 89 ++++++++++++++++++++++++++++-
doc/ctdbd.1.html | 143 ++++++++++++++++++++++++++++++++++++++++-------
doc/ctdbd.1.xml | 164 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
6 files changed, 582 insertions(+), 69 deletions(-)
Changeset truncated at 500 lines:
diff --git a/doc/ctdb.1 b/doc/ctdb.1
index 9dcf495..e9380f3 100644
--- a/doc/ctdb.1
+++ b/doc/ctdb.1
@@ -1,11 +1,11 @@
.\" Title: ctdb
.\" Author:
.\" Generator: DocBook XSL Stylesheets v1.71.0 <http://docbook.sf.net/>
-.\" Date: 03/04/2008
+.\" Date: 07/10/2008
.\" Manual:
.\" Source:
.\"
-.TH "CTDB" "1" "03/04/2008" "" ""
+.TH "CTDB" "1" "07/10/2008" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
@@ -68,6 +68,9 @@ You only need to specify this parameter if you run multiple ctdb daemons on the
.SH "ADMINISTRATIVE COMMANDS"
.PP
These are commands used to monitor and administrate a CTDB cluster.
+.SS "pnn"
+.PP
+This command displays the pnn of the current node.
.SS "status"
.PP
This command shows the current status of the ctdb node.
@@ -250,6 +253,44 @@ RecoveryBanPeriod = 300
.fi
.RE
+.SS "lvsmaster"
+.PP
+This command shows which node is currently the LVSMASTER. The LVSMASTER is the node in the cluster which drives the LVS system and which receives all incoming traffic from clients.
+.PP
+LVS is the mode where the entire CTDB/Samba cluster uses a single ip address for the entire cluster. In this mode all clients connect to one specific node which will then multiplex/loadbalance the clients evenly onto the other nodes in the cluster. This is an alternative to using public ip addresses. See the manpage for ctdbd for more information about LVS.
+.SS "lvs"
+.PP
+This command shows which nodes in the cluster are currently active in the LVS configuration. I.e. which nodes we are currently loadbalancing the single ip address across.
+.PP
+LVS will by default only loadbalance across those nodes that are both LVS capable and also HEALTHY. Except if all nodes are UNHEALTHY in which case LVS will loadbalance across all UNHEALTHY nodes as well. LVS will never use nodes that are DISCONNECTED, BANNED or DISABLED.
+.PP
+Example output:
+.sp
+.RS 3n
+.nf
+2:10.0.0.13
+3:10.0.0.14
+
+.fi
+.RE
+.SS "getcapabilities"
+.PP
+This command shows the capabilities of the current node. Please see manpage for ctdbd for a full list of all capabilities and more detailed description.
+.PP
+RECMASTER and LMASTER capabilities are primarily used when CTDBD is used to create a cluster spanning across WAN links. In which case ctdbd acts as a WAN accelerator.
+.PP
+LVS capabile means that the node is participating in LVS, a mode where the entire CTDB cluster uses one single ip address for the entire cluster instead of using public ip address failover. This is an alternative to using a loadbalancing layer\-4 switch.
+.PP
+Example output:
+.sp
+.RS 3n
+.nf
+RECMASTER: YES
+LMASTER: YES
+LVS: NO
+
+.fi
+.RE
.SS "statistics"
.PP
Collect statistics from the CTDB daemon about how many calls it has served.
diff --git a/doc/ctdb.1.html b/doc/ctdb.1.html
index 5fb9952..b9bbbd0 100644
--- a/doc/ctdb.1.html
+++ b/doc/ctdb.1.html
@@ -1,6 +1,6 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ctdb</title><meta name="generator" content="DocBook XSL Stylesheets V1.71.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="ctdb.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ctdb — clustered tdb database management utility</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="command">ctdb [ OPTIONS ] COMMAND ...</code> </p></div><div class="cmdsynopsis"><p><code class="command">ctdb</code> [-n <node>] [-Y] [-t <timeout>] [-T <timelimit>] [-? --help] [--usage] [-d --debug=<INTEGER>] [--socket=<filename>]</p></div></div><div class="refsect1" lang="en"><a name="id2480881"></a><h2>DESCRIPTION</h2><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ctdb</title><meta name="generator" content="DocBook XSL Stylesheets V1.71.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="ctdb.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ctdb — clustered tdb database management utility</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="command">ctdb [ OPTIONS ] COMMAND ...</code> </p></div><div class="cmdsynopsis"><p><code class="command">ctdb</code> [-n <node>] [-Y] [-t <timeout>] [-T <timelimit>] [-? --help] [--usage] [-d --debug=<INTEGER>] [--socket=<filename>]</p></div></div><div class="refsect1" lang="en"><a name="id2480874"></a><h2>DESCRIPTION</h2><p>
ctdb is a utility to view and manage a ctdb cluster.
- </p></div><div class="refsect1" lang="en"><a name="id2480890"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-n <pnn></span></dt><dd><p>
+ </p></div><div class="refsect1" lang="en"><a name="id2480884"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-n <pnn></span></dt><dd><p>
This specifies the physical node number on which to execute the
command. Default is to run the command on the deamon running on
the local host.
@@ -28,11 +28,13 @@
You only need to specify this parameter if you run multiple ctdb
daemons on the same physical host and thus can not use the default
name for the domain socket.
- </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481201"></a><h2>Administrative Commands</h2><p>
+ </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481194"></a><h2>Administrative Commands</h2><p>
These are commands used to monitor and administrate a CTDB cluster.
- </p><div class="refsect2" lang="en"><a name="id2481210"></a><h3>status</h3><p>
+ </p><div class="refsect2" lang="en"><a name="id2481203"></a><h3>pnn</h3><p>
+ This command displays the pnn of the current node.
+ </p></div><div class="refsect2" lang="en"><a name="id2481213"></a><h3>status</h3><p>
This command shows the current status of the ctdb node.
- </p><div class="refsect3" lang="en"><a name="id2481219"></a><h4>node status</h4><p>
+ </p><div class="refsect3" lang="en"><a name="id2481222"></a><h4>node status</h4><p>
Node status reflects the current status of the node. There are four possible states:
</p><p>
OK - This node is fully functional.
@@ -44,7 +46,7 @@
UNHEALTHY - A service provided by this node is malfunctioning and should be investigated. The CTDB daemon itself is operational and participates in the cluster. Its public IP address has been taken over by a different node and no services are currnetly being hosted. All unhealthy nodes should be investigated and require an administrative action to rectify.
</p><p>
BANNED - This node failed too many recovery attempts and has been banned from participating in the cluster for a period of RecoveryBanPeriod seconds. Any public IP address has been taken over by other nodes. This node does not provide any services. All banned nodes should be investigated and require an administrative action to rectify. This node does not perticipate in the CTDB cluster but can still be communicated with. I.e. ctdb commands can be sent to it.
- </p></div><div class="refsect3" lang="en"><a name="id2481270"></a><h4>generation</h4><p>
+ </p></div><div class="refsect3" lang="en"><a name="id2481273"></a><h4>generation</h4><p>
The generation id is a number that indicates the current generation
of a cluster instance. Each time a cluster goes through a
reconfiguration or a recovery its generation id will be changed.
@@ -65,10 +67,10 @@
All nodes start with generation "INVALID" and are not assigned a real
generation id until they have successfully been merged with a cluster
through a recovery.
- </p></div><div class="refsect3" lang="en"><a name="id2481306"></a><h4>VNNMAP</h4><p>
+ </p></div><div class="refsect3" lang="en"><a name="id2481308"></a><h4>VNNMAP</h4><p>
The list of Virtual Node Numbers. This is a list of all nodes that actively participates in the cluster and that share the workload of hosting the Clustered TDB database records.
Only nodes that are participating in the vnnmap can become lmaster or dmaster for a database record.
- </p></div><div class="refsect3" lang="en"><a name="id2481320"></a><h4>Recovery mode</h4><p>
+ </p></div><div class="refsect3" lang="en"><a name="id2481323"></a><h4>Recovery mode</h4><p>
This is the current recovery mode of the cluster. There are two possible modes:
</p><p>
NORMAL - The cluster is fully operational.
@@ -88,7 +90,7 @@
have been recovered, the node mode will change into NORMAL mode
and the databases will be "thawed", allowing samba to access the
databases again.
- </p></div><div class="refsect3" lang="en"><a name="id2528425"></a><h4>Recovery master</h4><p>
+ </p></div><div class="refsect3" lang="en"><a name="id2528429"></a><h4>Recovery master</h4><p>
This is the cluster node that is currently designated as the recovery master. This node is responsible of monitoring the consistency of the cluster and to perform the actual recovery process when reqired.
</p><p>
Only one node at a time can be the designated recovery master. Which
@@ -110,7 +112,7 @@ hash:2 lmaster:2
hash:3 lmaster:3
Recovery mode:NORMAL (0)
Recovery master:0
- </pre></div><div class="refsect2" lang="en"><a name="id2528458"></a><h3>ping</h3><p>
+ </pre></div><div class="refsect2" lang="en"><a name="id2528467"></a><h3>ping</h3><p>
This command will "ping" all CTDB daemons in the cluster to verify that they are processing commands correctly.
</p><p>
Example: ctdb ping
@@ -121,7 +123,7 @@ response from 0 time=0.000054 sec (3 clients)
response from 1 time=0.000144 sec (2 clients)
response from 2 time=0.000105 sec (2 clients)
response from 3 time=0.000114 sec (2 clients)
- </pre></div><div class="refsect2" lang="en"><a name="id2528484"></a><h3>ip</h3><p>
+ </pre></div><div class="refsect2" lang="en"><a name="id2528493"></a><h3>ip</h3><p>
This command will display the list of public addresses that are provided by the cluster and which physical node is currently serving this ip.
</p><p>
Example: ctdb ip
@@ -133,7 +135,7 @@ Number of addresses:4
12.1.1.2 1
12.1.1.3 2
12.1.1.4 3
- </pre></div><div class="refsect2" lang="en"><a name="id2528510"></a><h3>getvar <name></h3><p>
+ </pre></div><div class="refsect2" lang="en"><a name="id2528519"></a><h3>getvar <name></h3><p>
Get the runtime value of a tuneable variable.
</p><p>
Example: ctdb getvar MaxRedirectCount
@@ -141,11 +143,11 @@ Number of addresses:4
Example output:
</p><pre class="screen">
MaxRedirectCount = 3
- </pre></div><div class="refsect2" lang="en"><a name="id2528533"></a><h3>setvar <name> <value></h3><p>
+ </pre></div><div class="refsect2" lang="en"><a name="id2528542"></a><h3>setvar <name> <value></h3><p>
Set the runtime value of a tuneable variable.
</p><p>
Example: ctdb setvar MaxRedirectCount 5
- </p></div><div class="refsect2" lang="en"><a name="id2528547"></a><h3>listvars</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2528556"></a><h3>listvars</h3><p>
List all tuneable variables.
</p><p>
Example: ctdb listvars
@@ -167,7 +169,51 @@ MonitorInterval = 15
EventScriptTimeout = 20
RecoveryGracePeriod = 60
RecoveryBanPeriod = 300
- </pre></div><div class="refsect2" lang="en"><a name="id2528576"></a><h3>statistics</h3><p>
+ </pre></div><div class="refsect2" lang="en"><a name="id2528585"></a><h3>lvsmaster</h3><p>
+ This command shows which node is currently the LVSMASTER. The
+ LVSMASTER is the node in the cluster which drives the LVS system and
+ which receives all incoming traffic from clients.
+ </p><p>
+ LVS is the mode where the entire CTDB/Samba cluster uses a single
+ ip address for the entire cluster. In this mode all clients connect to
+ one specific node which will then multiplex/loadbalance the clients
+ evenly onto the other nodes in the cluster. This is an alternative to using
+ public ip addresses. See the manpage for ctdbd for more information
+ about LVS.
+ </p></div><div class="refsect2" lang="en"><a name="id2528607"></a><h3>lvs</h3><p>
+ This command shows which nodes in the cluster are currently active in the
+ LVS configuration. I.e. which nodes we are currently loadbalancing
+ the single ip address across.
+ </p><p>
+ LVS will by default only loadbalance across those nodes that are both
+ LVS capable and also HEALTHY. Except if all nodes are UNHEALTHY in which
+ case LVS will loadbalance across all UNHEALTHY nodes as well.
+ LVS will never use nodes that are DISCONNECTED, BANNED or DISABLED.
+ </p><p>
+ Example output:
+ </p><pre class="screen">
+2:10.0.0.13
+3:10.0.0.14
+ </pre></div><div class="refsect2" lang="en"><a name="id2528637"></a><h3>getcapabilities</h3><p>
+ This command shows the capabilities of the current node.
+ Please see manpage for ctdbd for a full list of all capabilities and
+ more detailed description.
+ </p><p>
+ RECMASTER and LMASTER capabilities are primarily used when CTDBD
+ is used to create a cluster spanning across WAN links. In which case
+ ctdbd acts as a WAN accelerator.
+ </p><p>
+ LVS capabile means that the node is participating in LVS, a mode
+ where the entire CTDB cluster uses one single ip address for the
+ entire cluster instead of using public ip address failover.
+ This is an alternative to using a loadbalancing layer-4 switch.
+ </p><p>
+ Example output:
+ </p><pre class="screen">
+RECMASTER: YES
+LMASTER: YES
+LVS: NO
+ </pre></div><div class="refsect2" lang="en"><a name="id2528673"></a><h3>statistics</h3><p>
Collect statistics from the CTDB daemon about how many calls it has served.
</p><p>
Example: ctdb statistics
@@ -209,11 +255,11 @@ CTDB version 1
max_hop_count 0
max_call_latency 4.948321 sec
max_lockwait_latency 0.000000 sec
- </pre></div><div class="refsect2" lang="en"><a name="id2528619"></a><h3>statisticsreset</h3><p>
+ </pre></div><div class="refsect2" lang="en"><a name="id2528716"></a><h3>statisticsreset</h3><p>
This command is used to clear all statistics counters in a node.
</p><p>
Example: ctdb statisticsreset
- </p></div><div class="refsect2" lang="en"><a name="id2528633"></a><h3>getdebug</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2528731"></a><h3>getdebug</h3><p>
Get the current debug level for the node. the debug level controls what information is written to the log file.
</p><p>
The debug levels are mapped to the corresponding syslog levels.
@@ -223,27 +269,27 @@ CTDB version 1
The list of debug levels from highest to lowest are :
</p><p>
EMERG ALERT CRIT ERR WARNING NOTICE INFO DEBUG
- </p></div><div class="refsect2" lang="en"><a name="id2528659"></a><h3>setdebug <debuglevel></h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2528756"></a><h3>setdebug <debuglevel></h3><p>
Set the debug level of a node. This controls what information will be logged.
</p><p>
The debuglevel is one of EMERG ALERT CRIT ERR WARNING NOTICE INFO DEBUG
- </p></div><div class="refsect2" lang="en"><a name="id2528675"></a><h3>getpid</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2528772"></a><h3>getpid</h3><p>
This command will return the process id of the ctdb daemon.
- </p></div><div class="refsect2" lang="en"><a name="id2528685"></a><h3>disable</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2528782"></a><h3>disable</h3><p>
This command is used to administratively disable a node in the cluster.
A disabled node will still participate in the cluster and host
clustered TDB records but its public ip address has been taken over by
a different node and it no longer hosts any services.
- </p></div><div class="refsect2" lang="en"><a name="id2528699"></a><h3>enable</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2528796"></a><h3>enable</h3><p>
Re-enable a node that has been administratively disabled.
- </p></div><div class="refsect2" lang="en"><a name="id2528709"></a><h3>ban <bantime|0></h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2528806"></a><h3>ban <bantime|0></h3><p>
Administratively ban a node for bantime seconds. A bantime of 0 means that the node should be permanently banned.
</p><p>
A banned node does not participate in the cluster and does not host any records for the clustered TDB. Its ip address has been taken over by an other node and no services are hosted.
</p><p>
Nodes are automatically banned if they are the cause of too many
cluster recoveries.
- </p></div><div class="refsect2" lang="en"><a name="id2528732"></a><h3>moveip <public_ip> <node></h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2528830"></a><h3>moveip <public_ip> <node></h3><p>
This command can be used to manually fail a public ip address to a
specific node.
</p><p>
@@ -254,19 +300,19 @@ CTDB version 1
DeterministicIPs = 0
</p><p>
NoIPFailback = 1
- </p></div><div class="refsect2" lang="en"><a name="id2528757"></a><h3>unban</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2528854"></a><h3>unban</h3><p>
This command is used to unban a node that has either been
administratively banned using the ban command or has been automatically
banned by the recovery daemon.
- </p></div><div class="refsect2" lang="en"><a name="id2528769"></a><h3>shutdown</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2528866"></a><h3>shutdown</h3><p>
This command will shutdown a specific CTDB daemon.
- </p></div><div class="refsect2" lang="en"><a name="id2528779"></a><h3>recover</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2528876"></a><h3>recover</h3><p>
This command will trigger the recovery daemon to do a cluster
recovery.
- </p></div><div class="refsect2" lang="en"><a name="id2528789"></a><h3>killtcp <srcip:port> <dstip:port></h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2528887"></a><h3>killtcp <srcip:port> <dstip:port></h3><p>
This command will kill the specified TCP connection by issuing a
TCP RST to the srcip:port endpoint.
- </p></div><div class="refsect2" lang="en"><a name="id2528801"></a><h3>reloadnodes</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2528898"></a><h3>reloadnodes</h3><p>
This command is used when adding new nodes to an existing cluster and
to reduce the disruption of this operation. This command should never
be used except when expanding an existing cluster.
@@ -290,7 +336,7 @@ CTDB version 1
5, Use 'ctdb status' on all nodes and verify that they now show the additional node.
</p><p>
6, Install and configure the new node and bring it online.
- </p></div><div class="refsect2" lang="en"><a name="id2528853"></a><h3>tickle <srcip:port> <dstip:port></h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2528950"></a><h3>tickle <srcip:port> <dstip:port></h3><p>
This command will will send a TCP tickle to the source host for the
specified TCP connection.
A TCP tickle is a TCP ACK packet with an invalid sequence and
@@ -302,7 +348,7 @@ CTDB version 1
TCP connection has been disrupted and that the client will need
to reestablish. This greatly speeds up the time it takes for a client
to detect and reestablish after an IP failover in the ctdb cluster.
- </p></div><div class="refsect2" lang="en"><a name="id2528877"></a><h3>repack [max_freelist]</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2528975"></a><h3>repack [max_freelist]</h3><p>
Over time, when records are created and deleted in a TDB, the TDB list of free space will become fragmented. This can lead to a slowdown in accessing TDB records.
This command is used to defragment a TDB database and pruning the freelist.
</p><p>
@@ -317,7 +363,7 @@ CTDB version 1
Example: ctdb repack 1000
</p><p>
By default, this operation is issued from the 00.ctdb event script every 5 minutes.
- </p></div><div class="refsect2" lang="en"><a name="id2528924"></a><h3>vacuum [max_records]</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2529021"></a><h3>vacuum [max_records]</h3><p>
Over time CTDB databases will fill up with empty deleted records which will lead to a progressive slow down of CTDB database access.
This command is used to prune all databases and delete all empty records from the cluster.
</p><p>
@@ -333,12 +379,12 @@ CTDB version 1
Example: ctdb vacuum
</p><p>
By default, this operation is issued from the 00.ctdb event script every 5 minutes.
- </p></div></div><div class="refsect1" lang="en"><a name="id2528961"></a><h2>Debugging Commands</h2><p>
+ </p></div></div><div class="refsect1" lang="en"><a name="id2529058"></a><h2>Debugging Commands</h2><p>
These commands are primarily used for CTDB development and testing and
should not be used for normal administration.
- </p><div class="refsect2" lang="en"><a name="id2528971"></a><h3>process-exists <pid></h3><p>
+ </p><div class="refsect2" lang="en"><a name="id2529068"></a><h3>process-exists <pid></h3><p>
This command checks if a specific process exists on the CTDB host. This is mainly used by Samba to check if remote instances of samba are still running or not.
- </p></div><div class="refsect2" lang="en"><a name="id2528983"></a><h3>getdbmap</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2529080"></a><h3>getdbmap</h3><p>
This command lists all clustered TDB databases that the CTDB daemon has attached to. Some databases are flagged as PERSISTENT, this means that the database stores data persistently and the data will remain across reboots. One example of such a database is secrets.tdb where information about how the cluster was joined to the domain is stored.
</p><p>
Most databases are not persistent and only store the state information that the currently running samba daemons need. These databases are always wiped when ctdb/samba starts and when a node is rebooted.
@@ -357,22 +403,22 @@ dbid:0x2672a57f name:idmap2.tdb path:/var/ctdb/persistent/idmap2.tdb.0 PERSISTEN
dbid:0xb775fff6 name:secrets.tdb path:/var/ctdb/persistent/secrets.tdb.0 PERSISTENT
dbid:0xe98e08b6 name:group_mapping.tdb path:/var/ctdb/persistent/group_mapping.tdb.0 PERSISTENT
dbid:0x7bbbd26c name:passdb.tdb path:/var/ctdb/persistent/passdb.tdb.0 PERSISTENT
- </pre></div><div class="refsect2" lang="en"><a name="id2529029"></a><h3>catdb <dbname></h3><p>
+ </pre></div><div class="refsect2" lang="en"><a name="id2529127"></a><h3>catdb <dbname></h3><p>
This command will dump a clustered TDB database to the screen. This is a debugging command.
- </p></div><div class="refsect2" lang="en"><a name="id2529040"></a><h3>getmonmode</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2529138"></a><h3>getmonmode</h3><p>
This command returns the monutoring mode of a node. The monitoring mode is either ACTIVE or DISABLED. Normally a node will continously monitor that all other nodes that are expected are in fact connected and that they respond to commands.
</p><p>
ACTIVE - This is the normal mode. The node is actively monitoring all other nodes, both that the transport is connected and also that the node responds to commands. If a node becomes unavailable, it will be marked as DISCONNECTED and a recovery is initiated to restore the cluster.
</p><p>
DISABLED - This node is not monitoring that other nodes are available. In this mode a node failure will not be detected and no recovery will be performed. This mode is useful when for debugging purposes one wants to attach GDB to a ctdb process but wants to prevent the rest of the cluster from marking this node as DISCONNECTED and do a recovery.
- </p></div><div class="refsect2" lang="en"><a name="id2529071"></a><h3>setmonmode <0|1></h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2529168"></a><h3>setmonmode <0|1></h3><p>
This command can be used to explicitely disable/enable monitoring mode on a node. The main purpose is if one wants to attach GDB to a running ctdb daemon but wants to prevent the other nodes from marking it as DISCONNECTED and issuing a recovery. To do this, set monitoring mode to 0 on all nodes before attaching with GDB. Remember to set monitoring mode back to 1 afterwards.
- </p></div><div class="refsect2" lang="en"><a name="id2529087"></a><h3>attach <dbname></h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2529184"></a><h3>attach <dbname></h3><p>
This is a debugging command. This command will make the CTDB daemon create a new CTDB database and attach to it.
- </p></div><div class="refsect2" lang="en"><a name="id2529098"></a><h3>dumpmemory</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2529195"></a><h3>dumpmemory</h3><p>
This is a debugging command. This command will make the ctdb
daemon to write a fill memory allocation map to standard output.
- </p></div><div class="refsect2" lang="en"><a name="id2529109"></a><h3>freeze</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2529207"></a><h3>freeze</h3><p>
This command will lock all the local TDB databases causing clients
that are accessing these TDBs such as samba3 to block until the
databases are thawed.
@@ -380,12 +426,12 @@ dbid:0x7bbbd26c name:passdb.tdb path:/var/ctdb/persistent/passdb.tdb.0 PERSISTEN
This is primarily used by the recovery daemon to stop all samba
daemons from accessing any databases while the database is recovered
and rebuilt.
- </p></div><div class="refsect2" lang="en"><a name="id2529128"></a><h3>thaw</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2529225"></a><h3>thaw</h3><p>
Thaw a previously frozen node.
- </p></div></div><div class="refsect1" lang="en"><a name="id2529138"></a><h2>SEE ALSO</h2><p>
+ </p></div></div><div class="refsect1" lang="en"><a name="id2529236"></a><h2>SEE ALSO</h2><p>
ctdbd(1), onnode(1)
<a href="http://ctdb.samba.org/" target="_top">http://ctdb.samba.org/</a>
- </p></div><div class="refsect1" lang="en"><a name="id2529151"></a><h2>COPYRIGHT/LICENSE</h2><div class="literallayout"><p><br>
+ </p></div><div class="refsect1" lang="en"><a name="id2529249"></a><h2>COPYRIGHT/LICENSE</h2><div class="literallayout"><p><br>
Copyright (C) Andrew Tridgell 2007<br>
Copyright (C) Ronnie sahlberg 2007<br>
<br>
diff --git a/doc/ctdb.1.xml b/doc/ctdb.1.xml
index d3d816f..19dbb92 100644
--- a/doc/ctdb.1.xml
+++ b/doc/ctdb.1.xml
@@ -130,6 +130,12 @@
These are commands used to monitor and administrate a CTDB cluster.
</para>
+ <refsect2><title>pnn</title>
+ <para>
+ This command displays the pnn of the current node.
+ </para>
+ </refsect2>
+
<refsect2><title>status</title>
<para>
This command shows the current status of the ctdb node.
@@ -340,6 +346,78 @@ RecoveryBanPeriod = 300
</screen>
</refsect2>
+ <refsect2><title>lvsmaster</title>
+ <para>
+ This command shows which node is currently the LVSMASTER. The
+ LVSMASTER is the node in the cluster which drives the LVS system and
+ which receives all incoming traffic from clients.
+ </para>
+ <para>
+ LVS is the mode where the entire CTDB/Samba cluster uses a single
+ ip address for the entire cluster. In this mode all clients connect to
+ one specific node which will then multiplex/loadbalance the clients
+ evenly onto the other nodes in the cluster. This is an alternative to using
+ public ip addresses. See the manpage for ctdbd for more information
+ about LVS.
+ </para>
+ </refsect2>
+
+ <refsect2><title>lvs</title>
+ <para>
+ This command shows which nodes in the cluster are currently active in the
+ LVS configuration. I.e. which nodes we are currently loadbalancing
+ the single ip address across.
+ </para>
+
+ <para>
+ LVS will by default only loadbalance across those nodes that are both
+ LVS capable and also HEALTHY. Except if all nodes are UNHEALTHY in which
+ case LVS will loadbalance across all UNHEALTHY nodes as well.
+ LVS will never use nodes that are DISCONNECTED, BANNED or DISABLED.
+ </para>
+
+ <para>
+ Example output:
+ </para>
+ <screen format="linespecific">
+2:10.0.0.13
+3:10.0.0.14
+ </screen>
+
+ </refsect2>
+
+
+ <refsect2><title>getcapabilities</title>
+ <para>
+ This command shows the capabilities of the current node.
+ Please see manpage for ctdbd for a full list of all capabilities and
+ more detailed description.
+ </para>
+
+ <para>
+ RECMASTER and LMASTER capabilities are primarily used when CTDBD
+ is used to create a cluster spanning across WAN links. In which case
+ ctdbd acts as a WAN accelerator.
+ </para>
+
+ <para>
+ LVS capabile means that the node is participating in LVS, a mode
+ where the entire CTDB cluster uses one single ip address for the
+ entire cluster instead of using public ip address failover.
+ This is an alternative to using a loadbalancing layer-4 switch.
+ </para>
+
+ <para>
+ Example output:
+ </para>
+ <screen format="linespecific">
+RECMASTER: YES
+LMASTER: YES
+LVS: NO
+ </screen>
+
+ </refsect2>
+
<refsect2><title>statistics</title>
<para>
Collect statistics from the CTDB daemon about how many calls it has served.
diff --git a/doc/ctdbd.1 b/doc/ctdbd.1
index baa7d51..858806b 100644
--- a/doc/ctdbd.1
+++ b/doc/ctdbd.1
@@ -1,11 +1,11 @@
.\" Title: ctdbd
.\" Author:
.\" Generator: DocBook XSL Stylesheets v1.71.0 <http://docbook.sf.net/>
-.\" Date: 03/04/2008
+.\" Date: 07/10/2008
.\" Manual:
.\" Source:
.\"
-.TH "CTDBD" "1" "03/04/2008" "" ""
+.TH "CTDBD" "1" "07/10/2008" "" ""
--
CTDB repository
More information about the samba-cvs
mailing list