[SCM] CTDB repository - branch master updated -
ctdb-1.0.86-59-g99f239f
Ronnie Sahlberg
sahlberg at samba.org
Thu Jul 9 03:53:07 GMT 2009
The branch, master has been updated
via 99f239f8b96c8c0a06ac8ca8b8083be96265865a (commit)
via d6ddea4167ccdad05e88378ee3f22b6125969562 (commit)
via 501a2747d839ca291b70c761098549cf6d47a158 (commit)
via 54b4a02053a0f98f8c424e7f658890254023d39a (commit)
via 866aa995dc029db6e510060e9e95a8ca149094ac (commit)
via 049271c83a09afb8d6c3e5212cf9ca782956b0c6 (commit)
via d47dab1026deba0554f21282a59bd172209ea066 (commit)
from 2ff6ee042080ba1c2bea76bbef3742997d84c9a8 (commit)
http://gitweb.samba.org/?p=sahlberg/ctdb.git;a=shortlog;h=master
- Log -----------------------------------------------------------------
commit 99f239f8b96c8c0a06ac8ca8b8083be96265865a
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date: Thu Jul 9 14:19:32 2009 +1000
recovery daemon needs to monitor when the local ctdb daemon is stopped and ensure that the databases gets frozen and the node enters recovery mode
commit d6ddea4167ccdad05e88378ee3f22b6125969562
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date: Thu Jul 9 13:07:15 2009 +1000
document the new commands ctdb stop/continue
commit 501a2747d839ca291b70c761098549cf6d47a158
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date: Thu Jul 9 13:20:14 2009 +1000
dont let other nodes modify the STOPPED flag for the local process when pushing out flags changes
commit 54b4a02053a0f98f8c424e7f658890254023d39a
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date: Thu Jul 9 12:22:46 2009 +1000
add two new controls, CTOP_NODE and CONTINUE_NODE
that are used to stop/continue a node instead of using modflags messages
commit 866aa995dc029db6e510060e9e95a8ca149094ac
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date: Thu Jul 9 11:57:20 2009 +1000
make it possible to start the daemon in STOPPED mode
commit 049271c83a09afb8d6c3e5212cf9ca782956b0c6
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date: Thu Jul 9 11:43:37 2009 +1000
remove the header printed for the machinereadable output for natgwlist
commit d47dab1026deba0554f21282a59bd172209ea066
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date: Thu Jul 9 11:38:18 2009 +1000
Add a new node flag : STOPPED
This node flag means the node is DISABLED and that all its public ip addresses
are failed over, but also that it has been removed from the VNNmap.
A STOPPED node should be in recovery mode active untill restarted using the continue command.
Adding two new commands "ctdb stop" "ctdb continue"
-----------------------------------------------------------------------
Summary of changes:
client/ctdb_client.c | 34 +++++++++++
config/ctdb.init | 1 +
doc/ctdb.1 | 38 +++++++-----
doc/ctdb.1.html | 150 ++++++++++++++++++++++++++---------------------
doc/ctdb.1.xml | 67 +++++++++++++++-------
doc/ctdbd.1 | 23 ++++++--
doc/ctdbd.1.html | 89 +++++++++++++++++------------
doc/ctdbd.1.xml | 31 +++++++++-
include/ctdb.h | 2 +
include/ctdb_private.h | 11 +++-
server/ctdb_control.c | 8 +++
server/ctdb_monitor.c | 10 +++
server/ctdb_recover.c | 16 +++++
server/ctdb_recoverd.c | 28 +++++++++
server/ctdb_server.c | 5 ++
server/ctdbd.c | 3 +
tcp/tcp_connect.c | 5 ++
tools/ctdb.c | 83 ++++++++++++++++++++++++--
18 files changed, 449 insertions(+), 155 deletions(-)
Changeset truncated at 500 lines:
diff --git a/client/ctdb_client.c b/client/ctdb_client.c
index 2c86b3e..4ea8d04 100644
--- a/client/ctdb_client.c
+++ b/client/ctdb_client.c
@@ -3707,3 +3707,37 @@ int ctdb_ctrl_setreclock(struct ctdb_context *ctdb, struct timeval timeout, uint
return 0;
}
+
+/*
+ stop a node
+ */
+int ctdb_ctrl_stop_node(struct ctdb_context *ctdb, struct timeval timeout, uint32_t destnode)
+{
+ int ret;
+
+ ret = ctdb_control(ctdb, destnode, 0, CTDB_CONTROL_STOP_NODE, 0, tdb_null,
+ ctdb, NULL, NULL, &timeout, NULL);
+ if (ret != 0) {
+ DEBUG(DEBUG_ERR,("Failed to stop node\n"));
+ return -1;
+ }
+
+ return 0;
+}
+
+/*
+ continue a node
+ */
+int ctdb_ctrl_continue_node(struct ctdb_context *ctdb, struct timeval timeout, uint32_t destnode)
+{
+ int ret;
+
+ ret = ctdb_control(ctdb, destnode, 0, CTDB_CONTROL_CONTINUE_NODE, 0, tdb_null,
+ ctdb, NULL, NULL, &timeout, NULL);
+ if (ret != 0) {
+ DEBUG(DEBUG_ERR,("Failed to continue node\n"));
+ return -1;
+ }
+
+ return 0;
+}
diff --git a/config/ctdb.init b/config/ctdb.init
index 95e8ccc..d69b01c 100755
--- a/config/ctdb.init
+++ b/config/ctdb.init
@@ -102,6 +102,7 @@ build_ctdb_options () {
maybe_set "-d" "$CTDB_DEBUGLEVEL"
maybe_set "--notification-script" "$CTDB_NOTIFY_SCRIPT"
maybe_set "--start-as-disabled" "$CTDB_START_AS_DISABLED" "yes"
+ maybe_set "--start-as-stopped " "$CTDB_START_AS_STOPPED" "yes"
maybe_set "--no-recmaster" "$CTDB_CAPABILITY_RECMASTER" "no"
maybe_set "--no-lmaster" "$CTDB_CAPABILITY_LMASTER" "no"
maybe_set "--lvs --single-public-ip" "$CTDB_LVS_PUBLIC_IP"
diff --git a/doc/ctdb.1 b/doc/ctdb.1
index dc6fc44..fd76a6a 100644
--- a/doc/ctdb.1
+++ b/doc/ctdb.1
@@ -1,11 +1,11 @@
.\" Title: ctdb
.\" Author:
.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
-.\" Date: 07/02/2009
+.\" Date: 07/09/2009
.\" Manual:
.\" Source:
.\"
-.TH "CTDB" "1" "07/02/2009" "" ""
+.TH "CTDB" "1" "07/09/2009" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
@@ -93,6 +93,8 @@ DISABLED \- This node has been administratively disabled\. This node is still fu
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\.
+.PP
+STOPPED \- A node that is stopped does not host any public ip addresses, nor is it part of the VNNMAP\. A stopped node can not become LVSMASTER, RECMASTER or NATGW\. 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
@@ -321,7 +323,7 @@ LVS is the mode where the entire CTDB/Samba cluster uses a single ip address for
.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\.
+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, STOPPED, BANNED or DISABLED\.
.PP
Example output:
.sp
@@ -445,13 +447,12 @@ This command is used to administratively disable a node in the cluster\. A disab
.SS "enable"
.PP
Re\-enable a node that has been administratively disabled\.
-.SS "ban <bantime|0>"
+.SS "stop"
.PP
-Administratively ban a node for bantime seconds\. A bantime of 0 means that the node should be permanently banned\.
+This command is used to administratively STOP a node in the cluster\. A STOPPED node is connected to the cluster but will not host any public ip addresse, nor does it participate in the VNNMAP\. The difference between a DISABLED node and a STOPPED node is that a STOPPED node does not host any parts of the database which means that a recovery is required to stop/continue nodes\.
+.SS "continue"
.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\.
-.PP
-Nodes are automatically banned if they are the cause of too many cluster recoveries\.
+Re\-start a node that has been administratively stopped\.
.SS "addip <public_ip/mask> <iface>"
.PP
This command is used to add a new public ip to a node during runtime\. This allows public addresses to be added to a cluster without having to restart the ctdb daemons\.
@@ -471,9 +472,6 @@ In order to manually override the "automatic" distribution of public ip addresse
DeterministicIPs = 0
.PP
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\.
.SS "shutdown"
.PP
This command will shutdown a specific CTDB daemon\.
@@ -553,6 +551,12 @@ Vacuum only deletes records where the local node is the lmaster\. To delete all
Example: ctdb vacuum
.PP
By default, this operation is issued from the 00\.ctdb event script every 5 minutes\.
+.SS "backupdb <database> <file>"
+.PP
+This command can be used to copy the entire content of a database out to a file\. This file can later be read back into ctdb using the restoredb command\. This is mainly useful for backing up persistent databases such as secrets\.tdb and similar\.
+.SS "restoredb <file>"
+.PP
+This command restores a persistent database that was previously backed up using backupdb\.
.SH "DEBUGGING COMMANDS"
.PP
These commands are primarily used for CTDB development and testing and should not be used for normal administration\.
@@ -617,12 +621,16 @@ Thaw a previously frozen node\.
.SS "eventscript <arguments>"
.PP
This is a debugging command\. This command can be used to manually invoke and run the eventscritps with arbitrary arguments\.
-.SS "backupdb <database> <file>"
+.SS "ban <bantime|0>"
.PP
-This command can be used to copy the entire content of a database out to a file\. This file can later be read back into ctdb using the restoredb command\. This is mainly useful for backing up persistent databases such as secrets\.tdb and similar\.
-.SS "restoredb <file>"
+Administratively ban a node for bantime seconds\. A bantime of 0 means that the node should be permanently banned\.
.PP
-This command restores a persistent database that was previously backed up using backupdb\.
+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\.
+.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\.
.SH "SEE ALSO"
.PP
ctdbd(1), onnode(1)
diff --git a/doc/ctdb.1.html b/doc/ctdb.1.html
index c589d72..82badbd 100644
--- a/doc/ctdb.1.html
+++ b/doc/ctdb.1.html
@@ -46,7 +46,13 @@
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="id2479754"></a><h4>generation</h4><p>
+ </p><p>
+ STOPPED - A node that is stopped does not host any public ip addresses,
+ nor is it part of the VNNMAP. A stopped node can not become LVSMASTER,
+ RECMASTER or NATGW.
+ 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="id2479763"></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.
@@ -67,10 +73,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="id2479789"></a><h4>VNNMAP</h4><p>
+ </p></div><div class="refsect3" lang="en"><a name="id2479798"></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="id2479803"></a><h4>Recovery mode</h4><p>
+ </p></div><div class="refsect3" lang="en"><a name="id2479812"></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.
@@ -90,7 +96,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="id2528502"></a><h4>Recovery master</h4><p>
+ </p></div><div class="refsect3" lang="en"><a name="id2528501"></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
@@ -112,9 +118,9 @@ hash:2 lmaster:2
hash:3 lmaster:3
Recovery mode:NORMAL (0)
Recovery master:0
- </pre></div><div class="refsect2" lang="en"><a name="id2528540"></a><h3>recmaster</h3><p>
+ </pre></div><div class="refsect2" lang="en"><a name="id2528538"></a><h3>recmaster</h3><p>
This command shows the pnn of the node which is currently the recmaster.
- </p></div><div class="refsect2" lang="en"><a name="id2528550"></a><h3>uptime</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2528549"></a><h3>uptime</h3><p>
This command shows the uptime for the ctdb daemon. When the last recovery completed and how long the last recovery took. If the "duration" is shown as a negative number, this indicates that there is a recovery in progress and it started that many seconds ago.
</p><p>
Example: ctdb uptime
@@ -123,7 +129,7 @@ Current time of node : Tue Mar 24 18:27:54 2009
Ctdbd start time : (000 00:00:05) Tue Mar 24 18:27:49 2009
Time of last recovery : (000 00:00:05) Tue Mar 24 18:27:49 2009
Duration of last recovery : 0.000000 seconds
- </pre></div><div class="refsect2" lang="en"><a name="id2528580"></a><h3>listnodes</h3><p>
+ </pre></div><div class="refsect2" lang="en"><a name="id2528579"></a><h3>listnodes</h3><p>
This command shows lists the ip addresses of all the nodes in the cluster.
</p><p>
Example: ctdb listnodes
@@ -132,7 +138,7 @@ Duration of last recovery : 0.000000 seconds
10.0.0.72
10.0.0.73
10.0.0.74
- </pre></div><div class="refsect2" lang="en"><a name="id2528604"></a><h3>ping</h3><p>
+ </pre></div><div class="refsect2" lang="en"><a name="id2528602"></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
@@ -143,7 +149,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="id2528630"></a><h3>ip</h3><p>
+ </pre></div><div class="refsect2" lang="en"><a name="id2528629"></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. By default this command will ONLY show those public addresses that are known to the node itself. To see the full list of all public ips across the cluster you must use "ctdb ip -n all".
</p><p>
Example: ctdb ip
@@ -155,7 +161,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="id2528658"></a><h3>scriptstatus</h3><p>
+ </pre></div><div class="refsect2" lang="en"><a name="id2528657"></a><h3>scriptstatus</h3><p>
This command displays which scripts where run in the previous monitoring cycle and the result of each script. If a script failed with an error, causing the node to become unhealthy, the output from that script is also shown.
</p><p>
Example: ctdb scriptstatus
@@ -171,7 +177,7 @@ Number of addresses:4
41.httpd Status:OK Duration:0.039 Tue Mar 24 18:56:57 2009
50.samba Status:ERROR Duration:0.082 Tue Mar 24 18:56:57 2009
OUTPUT:ERROR: Samba tcp port 445 is not responding
- </pre></div><div class="refsect2" lang="en"><a name="id2479836"></a><h3>getvar <name></h3><p>
+ </pre></div><div class="refsect2" lang="en"><a name="id2528693"></a><h3>getvar <name></h3><p>
Get the runtime value of a tuneable variable.
</p><p>
Example: ctdb getvar MaxRedirectCount
@@ -179,11 +185,11 @@ Number of addresses:4
Example output:
</p><pre class="screen">
MaxRedirectCount = 3
- </pre></div><div class="refsect2" lang="en"><a name="id2528713"></a><h3>setvar <name> <value></h3><p>
+ </pre></div><div class="refsect2" lang="en"><a name="id2528716"></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="id2528728"></a><h3>listvars</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2528731"></a><h3>listvars</h3><p>
List all tuneable variables.
</p><p>
Example: ctdb listvars
@@ -205,7 +211,7 @@ MonitorInterval = 15
EventScriptTimeout = 20
RecoveryGracePeriod = 60
RecoveryBanPeriod = 300
- </pre></div><div class="refsect2" lang="en"><a name="id2528755"></a><h3>lvsmaster</h3><p>
+ </pre></div><div class="refsect2" lang="en"><a name="id2528759"></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.
@@ -216,7 +222,7 @@ RecoveryBanPeriod = 300
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="id2528778"></a><h3>lvs</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2528781"></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.
@@ -224,13 +230,14 @@ RecoveryBanPeriod = 300
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 never use nodes that are DISCONNECTED, STOPPED, 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="id2528807"></a><h3>getcapabilities</h3><p>
+ </pre></div><div class="refsect2" lang="en"><a name="id2528811"></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.
@@ -249,7 +256,7 @@ RecoveryBanPeriod = 300
RECMASTER: YES
LMASTER: YES
LVS: NO
- </pre></div><div class="refsect2" lang="en"><a name="id2528844"></a><h3>statistics</h3><p>
+ </pre></div><div class="refsect2" lang="en"><a name="id2528847"></a><h3>statistics</h3><p>
Collect statistics from the CTDB daemon about how many calls it has served.
</p><p>
Example: ctdb statistics
@@ -291,23 +298,23 @@ 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="id2528887"></a><h3>statisticsreset</h3><p>
+ </pre></div><div class="refsect2" lang="en"><a name="id2528891"></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="id2528901"></a><h3>getreclock</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2528905"></a><h3>getreclock</h3><p>
This command is used to show the filename of the reclock file that is used.
</p><p>
Example output:
</p><pre class="screen">
Reclock file:/gpfs/.ctdb/shared
- </pre></div><div class="refsect2" lang="en"><a name="id2528921"></a><h3>setreclock [filename]</h3><p>
+ </pre></div><div class="refsect2" lang="en"><a name="id2528925"></a><h3>setreclock [filename]</h3><p>
This command is used to modify, or clear, the file that is used as the reclock file at runtime. When this command is used, the reclock file checks are disabled. To re-enable the checks the administrator needs to activate the "VerifyRecoveryLock" tunable using "ctdb setvar".
</p><p>
If run with no parameter this will remove the reclock file completely. If run with a parameter the parameter specifies the new filename to use for the recovery lock.
</p><p>
This command only affects the runtime settings of a ctdb node and will be lost when ctdb is restarted. For persistent changes to the reclock file setting you must edit /etc/sysconfig/ctdb.
- </p></div><div class="refsect2" lang="en"><a name="id2528948"></a><h3>getdebug</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2528951"></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.
@@ -317,40 +324,42 @@ Reclock file:/gpfs/.ctdb/shared
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="id2528974"></a><h3>setdebug <debuglevel></h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2528977"></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="id2528989"></a><h3>getpid</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2528993"></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="id2528999"></a><h3>disable</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2529003"></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="id2529013"></a><h3>enable</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2529017"></a><h3>enable</h3><p>
Re-enable a node that has been administratively disabled.
- </p></div><div class="refsect2" lang="en"><a name="id2529023"></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="id2529047"></a><h3>addip <public_ip/mask> <iface></h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2529027"></a><h3>stop</h3><p>
+ This command is used to administratively STOP a node in the cluster.
+ A STOPPED node is connected to the cluster but will not host any
+ public ip addresse, nor does it participate in the VNNMAP.
+ The difference between a DISABLED node and a STOPPED node is that
+ a STOPPED node does not host any parts of the database which means
+ that a recovery is required to stop/continue nodes.
+ </p></div><div class="refsect2" lang="en"><a name="id2529043"></a><h3>continue</h3><p>
+ Re-start a node that has been administratively stopped.
+ </p></div><div class="refsect2" lang="en"><a name="id2529053"></a><h3>addip <public_ip/mask> <iface></h3><p>
This command is used to add a new public ip to a node during runtime.
This allows public addresses to be added to a cluster without having
to restart the ctdb daemons.
</p><p>
Note that this only updates the runtime instance of ctdb. Any changes will be lost next time ctdb is restarted and the public addresses file is re-read.
If you want this change to be permanent you must also update the public addresses file manually.
- </p></div><div class="refsect2" lang="en"><a name="id2529067"></a><h3>delip <public_ip></h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2529073"></a><h3>delip <public_ip></h3><p>
This command is used to remove a public ip from a node during runtime.
If this public ip is currently hosted by the node it being removed from, the ip will first be failed over to another node, if possible, before it is removed.
</p><p>
Note that this only updates the runtime instance of ctdb. Any changes will be lost next time ctdb is restarted and the public addresses file is re-read.
If you want this change to be permanent you must also update the public addresses file manually.
- </p></div><div class="refsect2" lang="en"><a name="id2529088"></a><h3>moveip <public_ip> <node></h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2529094"></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>
@@ -361,26 +370,22 @@ Reclock file:/gpfs/.ctdb/shared
DeterministicIPs = 0
</p><p>
NoIPFailback = 1
- </p></div><div class="refsect2" lang="en"><a name="id2529113"></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="id2529125"></a><h3>shutdown</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2529119"></a><h3>shutdown</h3><p>
This command will shutdown a specific CTDB daemon.
- </p></div><div class="refsect2" lang="en"><a name="id2529135"></a><h3>recover</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2529129"></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="id2529145"></a><h3>ipreallocate</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2529139"></a><h3>ipreallocate</h3><p>
This command will force the recovery master to perform a full ip reallocation process and redistribute all ip addresses. This is useful to "reset" the allocations back to its default state if they have been changed using the "moveip" command. While a "recover" will also perform this reallocation, a recovery is much more hevyweight since it will also rebuild all the databases.
- </p></div><div class="refsect2" lang="en"><a name="id2529161"></a><h3>killtcp <srcip:port> <dstip:port></h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2529155"></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. This is a command used by the
ctdb eventscripts.
- </p></div><div class="refsect2" lang="en"><a name="id2529173"></a><h3>gratiousarp <ip> <interface></h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2529167"></a><h3>gratiousarp <ip> <interface></h3><p>
This command will send out a gratious arp for the specified interface
through the specified interface. This command is mainly used by the
ctdb eventscripts.
- </p></div><div class="refsect2" lang="en"><a name="id2529186"></a><h3>reloadnodes</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2529180"></a><h3>reloadnodes</h3><p>
This command is used when adding new nodes, or removing existing nodes from an existing cluster.
</p><p>
Procedure to add a node:
@@ -414,7 +419,7 @@ Reclock file:/gpfs/.ctdb/shared
</p><p>
5, Use 'ctdb status' on all nodes and verify that the deleted node no longer shows up in the list..
</p><p>
- </p></div><div class="refsect2" lang="en"><a name="id2529270"></a><h3>tickle <srcip:port> <dstip:port></h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2529264"></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
@@ -426,7 +431,7 @@ Reclock file:/gpfs/.ctdb/shared
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="id2529294"></a><h3>gettickles <ip></h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2529295"></a><h3>gettickles <ip></h3><p>
This command is used to show which TCP connections are registered with
CTDB to be "tickled" if there is a failover.
</p></div><div class="refsect2" lang="en"><a name="id2529306"></a><h3>repack [max_freelist]</h3><p>
@@ -460,12 +465,17 @@ Reclock file:/gpfs/.ctdb/shared
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="id2529389"></a><h2>Debugging Commands</h2><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2529388"></a><h3>backupdb <database> <file></h3><p>
+ This command can be used to copy the entire content of a database out to a file. This file can later be read back into ctdb using the restoredb command.
+This is mainly useful for backing up persistent databases such as secrets.tdb and similar.
+ </p></div><div class="refsect2" lang="en"><a name="id2529402"></a><h3>restoredb <file></h3><p>
+ This command restores a persistent database that was previously backed up using backupdb.
+ </p></div></div><div class="refsect1" lang="en"><a name="id2529414"></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="id2529399"></a><h3>process-exists <pid></h3><p>
+ </p><div class="refsect2" lang="en"><a name="id2529424"></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="id2529412"></a><h3>getdbmap</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2529437"></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.
@@ -484,25 +494,25 @@ 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="id2529470"></a><h3>catdb <dbname></h3><p>
+ </pre></div><div class="refsect2" lang="en"><a name="id2529489"></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="id2529481"></a><h3>getmonmode</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2529500"></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="id2529512"></a><h3>setmonmode <0|1></h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2529531"></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="id2529528"></a><h3>attach <dbname></h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2529546"></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="id2529539"></a><h3>dumpmemory</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2529558"></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="id2529550"></a><h3>rddumpmemory</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2476124"></a><h3>rddumpmemory</h3><p>
This is a debugging command. This command will dump the talloc memory
allocation tree for the recovery daemon to standard output.
- </p></div><div class="refsect2" lang="en"><a name="id2529562"></a><h3>freeze</h3><p>
+ </p></div><div class="refsect2" lang="en"><a name="id2476136"></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.
@@ -510,20 +520,26 @@ 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
--
CTDB repository
More information about the samba-cvs
mailing list