The branch, master has been updated
via a120c734c5425ebb2e09c2009374aa0bc5a432e8 (commit)
via 2583d0c8f9932e023b7377582f62c840e264be80 (commit)
via 1d5d13345086201fe55517aea5f8674ff3db1090 (commit)
via 2b70953cd51e879dc1fa113d68c6614051da5260 (commit)
via d1aa7953450de6ae215589404fb19e05edd3906f (commit)
via 666c3835376cd6b66aeaa110c76ecf052cd71a0a (commit)
via 616b71fef54a3d1ea2638602099722a19ef6f41d (commit)
via d6061214b4ef7e628ba7d27d81f23174c5364f67 (commit)
via a09864519d04f1e6a7ba498a795b6390183902a8 (commit)
via 082dd600ef25431efbf087ebf1957fbfd61cf104 (commit)
from 3ff0711fd3b288c153218ad33e8462a94b8d3275 (commit)
http://gitweb.samba.org/?p=sahlberg/ctdb.git;a=shortlog;h=master
- Log -----------------------------------------------------------------
commit a120c734c5425ebb2e09c2009374aa0bc5a432e8
Author: Ronnie Sahlberg <[EMAIL PROTECTED]>
Date: Mon Sep 15 07:04:26 2008 +1000
updates to the precompiled documentation
commit 2583d0c8f9932e023b7377582f62c840e264be80
Author: Martin Schwenke <[EMAIL PROTECTED]>
Date: Fri Sep 12 18:20:52 2008 +1000
Document the new descriptive node specifications.
Signed-off-by: Martin Schwenke <[EMAIL PROTECTED]>
commit 1d5d13345086201fe55517aea5f8674ff3db1090
Author: Martin Schwenke <[EMAIL PROTECTED]>
Date: Fri Sep 12 16:55:18 2008 +1000
onnode changes. "ok" is an alias for "healthy", "con" is an alias for
"connected". Allow "rm" or "recmaster" to be a nodespec for the
recovery master. Better error handling for interaction with ctdb
client.
Signed-off-by: Martin Schwenke <[EMAIL PROTECTED]>
commit 2b70953cd51e879dc1fa113d68c6614051da5260
Merge: d1aa7953450de6ae215589404fb19e05edd3906f
3ff0711fd3b288c153218ad33e8462a94b8d3275
Author: Martin Schwenke <[EMAIL PROTECTED]>
Date: Fri Sep 12 18:21:51 2008 +1000
Merge commit 'origin/master' into for-ronnie
commit d1aa7953450de6ae215589404fb19e05edd3906f
Author: Martin Schwenke <[EMAIL PROTECTED]>
Date: Fri Sep 12 11:22:50 2008 +1000
Changes to onnode. Add "healthy" and "connected" as possible
nodespecs. Since we're now explicitly using bash, use local variables
when sensible.
Signed-off-by: Martin Schwenke <[EMAIL PROTECTED]>
commit 666c3835376cd6b66aeaa110c76ecf052cd71a0a
Merge: 616b71fef54a3d1ea2638602099722a19ef6f41d
a72f5b7d1560e427e18b1c55a2932a7fb037f4c7
Author: Martin Schwenke <[EMAIL PROTECTED]>
Date: Fri Sep 12 11:26:25 2008 +1000
Merge commit 'origin/master' into for-ronnie
commit 616b71fef54a3d1ea2638602099722a19ef6f41d
Author: Martin Schwenke <[EMAIL PROTECTED]>
Date: Fri Sep 12 10:36:15 2008 +1000
Minor documentation fixes.
Signed-off-by: Martin Schwenke <[EMAIL PROTECTED]>
commit d6061214b4ef7e628ba7d27d81f23174c5364f67
Author: Martin Schwenke <[EMAIL PROTECTED]>
Date: Fri Jul 11 15:05:41 2008 +1000
Signed-off-by: Martin Schwenke <[EMAIL PROTECTED]>
Minor updates to doc/onnode.1.xml.
commit a09864519d04f1e6a7ba498a795b6390183902a8
Author: Martin Schwenke <[EMAIL PROTECTED]>
Date: Fri Jul 11 14:57:24 2008 +1000
Signed-off-by: Martin Schwenke <[EMAIL PROTECTED]>
Minor fix to tools/onnode usage message.
commit 082dd600ef25431efbf087ebf1957fbfd61cf104
Author: Martin Schwenke <[EMAIL PROTECTED]>
Date: Fri Jul 11 12:52:01 2008 +1000
Signed-off-by: Martin Schwenke <[EMAIL PROTECTED]>
In tools/onnode, remove reference to -t option in usage message.
-----------------------------------------------------------------------
Summary of changes:
doc/ctdb.1 | 296 +++++++++++++++++++++++++-------------------------
doc/ctdb.1.html | 98 ++++++++--------
doc/ctdb.1.xml | 2 +-
doc/ctdbd.1 | 319 ++++++++++++++++++++++++++---------------------------
doc/ctdbd.1.html | 72 ++++++------
doc/ctdbd.1.xml | 22 ++--
doc/onnode.1 | 8 +-
doc/onnode.1.html | 16 ++--
doc/onnode.1.xml | 65 +++++++++--
tools/onnode | 103 +++++++++++++++---
10 files changed, 556 insertions(+), 445 deletions(-)
Changeset truncated at 500 lines:
diff --git a/doc/ctdb.1 b/doc/ctdb.1
index e9380f3..5da61bf 100644
--- a/doc/ctdb.1
+++ b/doc/ctdb.1
@@ -1,165 +1,165 @@
.\" Title: ctdb
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.71.0 <http://docbook.sf.net/>
-.\" Date: 07/10/2008
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\" Date: 09/15/2008
.\" Manual:
.\" Source:
.\"
-.TH "CTDB" "1" "07/10/2008" "" ""
+.TH "CTDB" "1" "09/15/2008" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.SH "NAME"
-ctdb \- clustered tdb database management utility
+ctdb - clustered tdb database management utility
.SH "SYNOPSIS"
.HP 29
-\fBctdb [ OPTIONS ] COMMAND ...\fR
+\fBctdb [ OPTIONS ] COMMAND \.\.\.\fR
.HP 5
\fBctdb\fR [\-n\ <node>] [\-Y] [\-t\ <timeout>] [\-T\ <timelimit>] [\-?\
\-\-help] [\-\-usage] [\-d\ \-\-debug=<INTEGER>] [\-\-socket=<filename>]
.SH "DESCRIPTION"
.PP
-ctdb is a utility to view and manage a ctdb cluster.
+ctdb is a utility to view and manage a ctdb cluster\.
.SH "OPTIONS"
.PP
\-n <pnn>
-.RS 3n
-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.
+.RS 4
+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\.
.sp
-The physical node number is an integer that describes the node in the cluster.
The first node has physical node number 0.
+The physical node number is an integer that describes the node in the
cluster\. The first node has physical node number 0\.
.RE
.PP
\-Y
-.RS 3n
-Produce output in machine readable form for easier parsing by scripts. Not all
commands support this option.
+.RS 4
+Produce output in machine readable form for easier parsing by scripts\. Not
all commands support this option\.
.RE
.PP
\-t <timeout>
-.RS 3n
-How long should ctdb wait for the local ctdb daemon to respond to a command
before timing out. Default is 3 seconds.
+.RS 4
+How long should ctdb wait for the local ctdb daemon to respond to a command
before timing out\. Default is 3 seconds\.
.RE
.PP
\-T <timelimit>
-.RS 3n
-A limit on how long the ctdb command will run for before it will be aborted.
When this timelimit has been exceeded the ctdb command will terminate.
+.RS 4
+A limit on how long the ctdb command will run for before it will be aborted\.
When this timelimit has been exceeded the ctdb command will terminate\.
.RE
.PP
\-? \-\-help
-.RS 3n
-Print some help text to the screen.
+.RS 4
+Print some help text to the screen\.
.RE
.PP
\-\-usage
-.RS 3n
-Print useage information to the screen.
+.RS 4
+Print useage information to the screen\.
.RE
.PP
\-d \-\-debug=<debuglevel>
-.RS 3n
-Change the debug level for the command. Default is 0.
+.RS 4
+Change the debug level for the command\. Default is 0\.
.RE
.PP
\-\-socket=<filename>
-.RS 3n
-Specify the socketname to use when connecting to the local ctdb daemon. The
default is /tmp/ctdb.socket .
+.RS 4
+Specify the socketname to use when connecting to the local ctdb daemon\. The
default is /tmp/ctdb\.socket \.
.sp
-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.
+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\.
.RE
.SH "ADMINISTRATIVE COMMANDS"
.PP
-These are commands used to monitor and administrate a CTDB cluster.
+These are commands used to monitor and administrate a CTDB cluster\.
.SS "pnn"
.PP
-This command displays the pnn of the current node.
+This command displays the pnn of the current node\.
.SS "status"
.PP
-This command shows the current status of the ctdb node.
+This command shows the current status of the ctdb node\.
.sp
.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1
.br
-\fBnode status\fR
+node status
.RS
.PP
-Node status reflects the current status of the node. There are four possible
states:
+Node status reflects the current status of the node\. There are five possible
states:
.PP
-OK \- This node is fully functional.
+OK \- This node is fully functional\.
.PP
-DISCONNECTED \- This node could not be connected through the network and is
currently not participating in the cluster. If there is a public IP address
associated with this node it should have been taken over by a different node.
No services are running on this node.
+DISCONNECTED \- This node could not be connected through the network and is
currently not participating in the cluster\. If there is a public IP address
associated with this node it should have been taken over by a different node\.
No services are running on this node\.
.PP
-DISABLED \- This node has been administratively disabled. This node is still
functional and participates in the CTDB cluster but its IP addresses have been
taken over by a different node and no services are currently being hosted.
+DISABLED \- This node has been administratively disabled\. This node is still
functional and participates in the CTDB cluster but its IP addresses have been
taken over by a different node and no services are currently being hosted\.
.PP
-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.
+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\.
.PP
-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.
+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\.
.RE
.sp
.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1
.br
-\fBgeneration\fR
+generation
.RS
.PP
-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.
+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\.
.PP
-This number does not have any particular meaning other than to keep track of
when a cluster has gone through a recovery. It is a random number that
represents the current instance of a ctdb cluster and its databases. CTDBD uses
this number internally to be able to tell when commands to operate on the
cluster and the databases was issued in a different generation of the cluster,
to ensure that commands that operate on the databases will not survive across a
cluster database recovery. After a recovery, all old outstanding commands will
automatically become invalid.
+This number does not have any particular meaning other than to keep track of
when a cluster has gone through a recovery\. It is a random number that
represents the current instance of a ctdb cluster and its databases\. CTDBD
uses this number internally to be able to tell when commands to operate on the
cluster and the databases was issued in a different generation of the cluster,
to ensure that commands that operate on the databases will not survive across a
cluster database recovery\. After a recovery, all old outstanding commands will
automatically become invalid\.
.PP
-Sometimes this number will be shown as "INVALID". This only means that the
ctdbd daemon has started but it has not yet merged with the cluster through a
recovery. 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.
+Sometimes this number will be shown as "INVALID"\. This only means that the
ctdbd daemon has started but it has not yet merged with the cluster through a
recovery\. 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\.
.RE
.sp
.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1
.br
-\fBVNNMAP\fR
+VNNMAP
.RS
.PP
-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.
+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\.
.RE
.sp
.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1
.br
-\fBRecovery mode\fR
+Recovery mode
.RS
.PP
-This is the current recovery mode of the cluster. There are two possible modes:
+This is the current recovery mode of the cluster\. There are two possible
modes:
.PP
-NORMAL \- The cluster is fully operational.
+NORMAL \- The cluster is fully operational\.
.PP
-RECOVERY \- The cluster databases have all been frozen, pausing all services
while the cluster awaits a recovery process to complete. A recovery process
should finish within seconds. If a cluster is stuck in the RECOVERY state this
would indicate a cluster malfunction which needs to be investigated.
+RECOVERY \- The cluster databases have all been frozen, pausing all services
while the cluster awaits a recovery process to complete\. A recovery process
should finish within seconds\. If a cluster is stuck in the RECOVERY state this
would indicate a cluster malfunction which needs to be investigated\.
.PP
-Once the recovery master detects an inconsistency, for example a node becomes
disconnected/connected, the recovery daemon will trigger a cluster recovery
process, where all databases are remerged across the cluster. When this process
starts, the recovery master will first "freeze" all databases to prevent
applications such as samba from accessing the databases and it will also mark
the recovery mode as RECOVERY.
+Once the recovery master detects an inconsistency, for example a node becomes
disconnected/connected, the recovery daemon will trigger a cluster recovery
process, where all databases are remerged across the cluster\. When this
process starts, the recovery master will first "freeze" all databases to
prevent applications such as samba from accessing the databases and it will
also mark the recovery mode as RECOVERY\.
.PP
-When CTDBD starts up, it will start in RECOVERY mode. Once the node has been
merged into a cluster and all databases have been recovered, the node mode will
change into NORMAL mode and the databases will be "thawed", allowing samba to
access the databases again.
+When CTDBD starts up, it will start in RECOVERY mode\. Once the node has been
merged into a cluster and all databases have been recovered, the node mode will
change into NORMAL mode and the databases will be "thawed", allowing samba to
access the databases again\.
.RE
.sp
.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1
.br
-\fBRecovery master\fR
+Recovery master
.RS
.PP
-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.
+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\.
.PP
-Only one node at a time can be the designated recovery master. Which node is
designated the recovery master is decided by an election process in the
recovery daemons running on each node.
+Only one node at a time can be the designated recovery master\. Which node is
designated the recovery master is decided by an election process in the
recovery daemons running on each node\.
.RE
.PP
Example: ctdb status
.PP
Example output:
.sp
-.RS 3n
+.RS 4
.nf
Number of nodes:4
-pnn:0 11.1.2.200 OK (THIS NODE)
-pnn:1 11.1.2.201 OK
-pnn:2 11.1.2.202 OK
-pnn:3 11.1.2.203 OK
+pnn:0 11\.1\.2\.200 OK (THIS NODE)
+pnn:1 11\.1\.2\.201 OK
+pnn:2 11\.1\.2\.202 OK
+pnn:3 11\.1\.2\.203 OK
Generation:1362079228
Size:4
hash:0 lmaster:0
@@ -173,48 +173,48 @@ Recovery master:0
.RE
.SS "ping"
.PP
-This command will "ping" all CTDB daemons in the cluster to verify that they
are processing commands correctly.
+This command will "ping" all CTDB daemons in the cluster to verify that they
are processing commands correctly\.
.PP
Example: ctdb ping
.PP
Example output:
.sp
-.RS 3n
+.RS 4
.nf
-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)
+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)
.fi
.RE
.SS "ip"
.PP
-This command will display the list of public addresses that are provided by
the cluster and which physical node is currently serving this ip.
+This command will display the list of public addresses that are provided by
the cluster and which physical node is currently serving this ip\.
.PP
Example: ctdb ip
.PP
Example output:
.sp
-.RS 3n
+.RS 4
.nf
Number of addresses:4
-12.1.1.1 0
-12.1.1.2 1
-12.1.1.3 2
-12.1.1.4 3
+12\.1\.1\.1 0
+12\.1\.1\.2 1
+12\.1\.1\.3 2
+12\.1\.1\.4 3
.fi
.RE
.SS "getvar <name>"
.PP
-Get the runtime value of a tuneable variable.
+Get the runtime value of a tuneable variable\.
.PP
Example: ctdb getvar MaxRedirectCount
.PP
Example output:
.sp
-.RS 3n
+.RS 4
.nf
MaxRedirectCount = 3
@@ -222,18 +222,18 @@ MaxRedirectCount = 3
.RE
.SS "setvar <name> <value>"
.PP
-Set the runtime value of a tuneable variable.
+Set the runtime value of a tuneable variable\.
.PP
Example: ctdb setvar MaxRedirectCount 5
.SS "listvars"
.PP
-List all tuneable variables.
+List all tuneable variables\.
.PP
Example: ctdb listvars
.PP
Example output:
.sp
-.RS 3n
+.RS 4
.nf
MaxRedirectCount = 5
SeqnumFrequency = 1
@@ -255,35 +255,35 @@ RecoveryBanPeriod = 300
.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.
+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.
+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.
+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.
+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
+.RS 4
.nf
-2:10.0.0.13
-3:10.0.0.14
+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.
+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.
+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.
+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
+.RS 4
.nf
RECMASTER: YES
LMASTER: YES
@@ -293,13 +293,13 @@ LVS: NO
.RE
.SS "statistics"
.PP
-Collect statistics from the CTDB daemon about how many calls it has served.
+Collect statistics from the CTDB daemon about how many calls it has served\.
.PP
Example: ctdb statistics
.PP
Example output:
.sp
-.RS 3n
+.RS 4
.nf
CTDB version 1
num_clients 3
@@ -334,49 +334,49 @@ CTDB version 1
pending_lockwait_calls 0
memory_used 5040
max_hop_count 0
- max_call_latency 4.948321 sec
- max_lockwait_latency 0.000000 sec
+ max_call_latency 4\.948321 sec
+ max_lockwait_latency 0\.000000 sec
.fi
.RE
.SS "statisticsreset"
.PP
-This command is used to clear all statistics counters in a node.
+This command is used to clear all statistics counters in a node\.
.PP
Example: ctdb statisticsreset
.SS "getdebug"
.PP
-Get the current debug level for the node. the debug level controls what
information is written to the log file.
+Get the current debug level for the node\. the debug level controls what
information is written to the log file\.
.PP
-The debug levels are mapped to the corresponding syslog levels. When a debug
level is set, only those messages at that level and higher levels will be
printed.
+The debug levels are mapped to the corresponding syslog levels\. When a debug
level is set, only those messages at that level and higher levels will be
printed\.
.PP
The list of debug levels from highest to lowest are :
.PP
EMERG ALERT CRIT ERR WARNING NOTICE INFO DEBUG
.SS "setdebug <debuglevel>"
.PP
-Set the debug level of a node. This controls what information will be logged.
+Set the debug level of a node\. This controls what information will be logged\.
.PP
The debuglevel is one of EMERG ALERT CRIT ERR WARNING NOTICE INFO DEBUG
.SS "getpid"
.PP
-This command will return the process id of the ctdb daemon.
+This command will return the process id of the ctdb daemon\.
.SS "disable"
.PP
-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.
+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\.
.SS "enable"
.PP
-Re\-enable a node that has been administratively disabled.
+Re\-enable a node that has been administratively disabled\.
.SS "ban <bantime|0>"
.PP
-Administratively ban a node for bantime seconds. A bantime of 0 means that the
node should be permanently banned.
+Administratively ban a node for bantime seconds\. A bantime of 0 means that
the node should be permanently banned\.
.PP
-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.
+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\.
.PP
-Nodes are automatically banned if they are the cause of too many cluster
recoveries.
+Nodes are automatically banned if they are the cause of too many cluster
recoveries\.
.SS "moveip <public_ip> <node>"
.PP
-This command can be used to manually fail a public ip address to a specific
node.
+This command can be used to manually fail a public ip address to a specific
node\.
.PP
In order to manually override the "automatic" distribution of public ip
addresses that ctdb normally provides, this command only works when you have
changed the tunables for the daemon to:
.PP
@@ -385,129 +385,129 @@ DeterministicIPs = 0
NoIPFailback = 1
.SS "unban"
.PP
-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.
+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\.
.SS "shutdown"
.PP
-This command will shutdown a specific CTDB daemon.
+This command will shutdown a specific CTDB daemon\.
.SS "recover"
.PP
-This command will trigger the recovery daemon to do a cluster recovery.
+This command will trigger the recovery daemon to do a cluster recovery\.
.SS "killtcp <srcip:port> <dstip:port>"
.PP
-This command will kill the specified TCP connection by issuing a TCP RST to
the srcip:port endpoint.
+This command will kill the specified TCP connection by issuing a TCP RST to
the srcip:port endpoint\.
.SS "reloadnodes"
.PP
-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. This can only be used to expand a
cluster. To remove a node from the cluster you still need to shut down ctdb on
all nodes, edit the nodes file and restart ctdb.
+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\. This can only be used to expand a
cluster\. To remove a node from the cluster you still need to shut down ctdb on
all nodes, edit the nodes file and restart ctdb\.
.PP
Procedure:
.PP
-1, To expand an existing cluster, first ensure with 'ctdb status' that all
nodes are up and running and that they are all healthy. Do not try to expand a
cluster unless it is completely healthy!
+1, To expand an existing cluster, first ensure with \'ctdb status\' that all
nodes are up and running and that they are all healthy\. Do not try to expand a
cluster unless it is completely healthy!
.PP
-2, On all nodes, edit /etc/ctdb/nodes and add the new node as the last entry
to the file. The new node MUST be added to the end of this file!
+2, On all nodes, edit /etc/ctdb/nodes and add the new node as the last entry
to the file\. The new node MUST be added to the end of this file!
.PP
3, Verify that all the nodes have identical /etc/ctdb/nodes files after you
edited them and added the new node!
.PP
-4, Run 'ctdb reloadnodes' to force all nodes to reaload the nodesfile.
+4, Run \'ctdb reloadnodes\' to force all nodes to reaload the nodesfile\.
.PP
-5, Use 'ctdb status' on all nodes and verify that they now show the additional
node.
+5, Use \'ctdb status\' on all nodes and verify that they now show the
additional node\.
.PP
-6, Install and configure the new node and bring it online.
+6, Install and configure the new node and bring it online\.
.SS "tickle <srcip:port> <dstip:port>"
.PP
-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
acknowledge number and will when received by the source host result in it
sending an immediate correct ACK back to the other end.
+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
acknowledge number and will when received by the source host result in it
sending an immediate correct ACK back to the other end\.
.PP
-TCP tickles are useful to "tickle" clients after a IP failover has occured
since this will make the client immediately recognize the 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.
+TCP tickles are useful to "tickle" clients after a IP failover has occured
since this will make the client immediately recognize the 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\.
.SS "repack [max_freelist]"
.PP
-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.
+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\.
.PP
-If [max_freelist] is specified, then a database will only be repacked if it
has more than this number of entries in the freelist.
+If [max_freelist] is specified, then a database will only be repacked if it
has more than this number of entries in the freelist\.
.PP
-During repacking of the database, the entire TDB database will be locked to
prevent writes. If samba tries to write to a record in the database during a
repack operation, samba will block until the repacking has completed.
+During repacking of the database, the entire TDB database will be locked to
prevent writes\. If samba tries to write to a record in the database during a
repack operation, samba will block until the repacking has completed\.
.PP
-This command can be disruptive and can cause samba to block for the duration
of the repack operation. In general, a repack operation will take less than one
second to complete.
+This command can be disruptive and can cause samba to block for the duration
of the repack operation\. In general, a repack operation will take less than
one second to complete\.
.PP
-A repack operation will only defragment the local TDB copy of the CTDB
database. You need to run this command on all of the nodes to repack a CTDB
database completely.
+A repack operation will only defragment the local TDB copy of the CTDB
database\. You need to run this command on all of the nodes to repack a CTDB
database completely\.
.PP
--
CTDB repository
