[SCM] CTDB repository - branch master updated - ctdb-1.13-17-g0ae2a46
Ronnie Sahlberg
sahlberg at samba.org
Tue Mar 20 00:47:04 MDT 2012
The branch, master has been updated
via 0ae2a46e37df8d84ce0c76b7a5d32d6e93af709b (commit)
via e6a8306257dece02313043274789b52cef1a5647 (commit)
via d0d98f7e45e5084b81335b004d50bddc80cdc219 (commit)
via cf96d6380de974c1abff7a33c62a7e31ac980551 (commit)
via 035c0d981bde8c0eee8b3f24ba8e2dc817e5b504 (commit)
via 1c976d83b1d7dac6f0ef81306774998e4c8b56a1 (commit)
via 05923a14bc8ae8e3c5cda28ff4e0fb0d473d5f7d (commit)
via c37aa6f3738693653f64c2fa015ace061da38b5a (commit)
via eafd7bbaaa5931546a96c8beae3cf9a39a49c925 (commit)
via 7d3931298e6477d92f43652c3006b0c426cb1307 (commit)
from af72f8bc05f78983f9624d81788f9d89af474b11 (commit)
http://gitweb.samba.org/?p=ctdb.git;a=shortlog;h=master
- Log -----------------------------------------------------------------
commit 0ae2a46e37df8d84ce0c76b7a5d32d6e93af709b
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date: Tue Mar 20 17:43:26 2012 +1100
DOC regenerate the manpage
commit e6a8306257dece02313043274789b52cef1a5647
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date: Tue Mar 20 17:07:13 2012 +1100
STICKY document the sticky record parameters
commit d0d98f7e45e5084b81335b004d50bddc80cdc219
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date: Tue Mar 20 16:58:35 2012 +1100
STICKY: add prototype code to make records stick to a node to "calm" down if they are found to be very hot and accessed by a lot of clients.
This can improve performance and stop clients from having to chase a rapidly migrating/bouncing record
commit cf96d6380de974c1abff7a33c62a7e31ac980551
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date: Tue Mar 20 12:25:47 2012 +1100
DOC: Document the MaxLACount tunable variable
commit 035c0d981bde8c0eee8b3f24ba8e2dc817e5b504
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date: Tue Mar 20 12:20:55 2012 +1100
LACOUNT: Add back lacount mechanism to defer migrating a fetched/read copy until after default of 20 consecutive requests from the same node
This can improve performance slightly on certain workloads where smbds frequently read from the same record
commit 1c976d83b1d7dac6f0ef81306774998e4c8b56a1
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date: Tue Mar 20 12:08:12 2012 +1100
STATISTICS: add per-db hop count statistics
commit 05923a14bc8ae8e3c5cda28ff4e0fb0d473d5f7d
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date: Tue Mar 20 11:43:09 2012 +1100
CTDB: change how the hop count buckets are displayed in ctdb statistics
commit c37aa6f3738693653f64c2fa015ace061da38b5a
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date: Tue Mar 20 11:38:20 2012 +1100
DOC document the FetchCollapse tunable
commit eafd7bbaaa5931546a96c8beae3cf9a39a49c925
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date: Tue Mar 20 11:31:59 2012 +1100
FETCH COLLAPSE : Change the fetch-lock collapse to collapse ALL fetches, including fetch-locks into a single command in flight per record. Also add a tunable to enable/disable this optimization for hot records
commit 7d3931298e6477d92f43652c3006b0c426cb1307
Author: Ronnie Sahlberg <ronniesahlberg at gmail.com>
Date: Wed Mar 7 17:02:41 2012 +1100
add max hop count buckets to see how bad hopcounts are
-----------------------------------------------------------------------
Summary of changes:
client/ctdb_client.c | 52 ++++-
common/ctdb_ltdb.c | 1 +
doc/ctdbd.1 | 684 ++++++++++++++++++++++++++++-----------------
doc/ctdbd.1.html | 175 +++++++-----
doc/ctdbd.1.xml | 71 +++++
include/ctdb_client.h | 6 +
include/ctdb_private.h | 11 +-
include/ctdb_protocol.h | 8 +-
server/ctdb_call.c | 282 ++++++++++++++++++-
server/ctdb_control.c | 11 +
server/ctdb_daemon.c | 13 +-
server/ctdb_ltdb_server.c | 22 ++
server/ctdb_recover.c | 3 +
server/ctdb_tunables.c | 7 +-
tools/ctdb.c | 85 ++++++-
15 files changed, 1083 insertions(+), 348 deletions(-)
Changeset truncated at 500 lines:
diff --git a/client/ctdb_client.c b/client/ctdb_client.c
index 1b41439..b01e258 100644
--- a/client/ctdb_client.c
+++ b/client/ctdb_client.c
@@ -71,7 +71,7 @@ struct ctdb_req_header *_ctdbd_allocate_pkt(struct ctdb_context *ctdb,
*/
int ctdb_call_local(struct ctdb_db_context *ctdb_db, struct ctdb_call *call,
struct ctdb_ltdb_header *header, TALLOC_CTX *mem_ctx,
- TDB_DATA *data, bool updatetdb)
+ TDB_DATA *data, bool updatetdb, uint32_t caller)
{
struct ctdb_call_info *c;
struct ctdb_registered_call *fn;
@@ -106,7 +106,15 @@ int ctdb_call_local(struct ctdb_db_context *ctdb_db, struct ctdb_call *call,
}
/* we need to force the record to be written out if this was a remote access */
- if (c->new_data == NULL) {
+ if (header->laccessor != caller) {
+ header->lacount = 0;
+ }
+ header->laccessor = caller;
+ header->lacount++;
+
+ /* we need to force the record to be written out if this was a remote access,
+ so that the lacount is updated */
+ if (c->new_data == NULL && header->laccessor != ctdb->pnn) {
c->new_data = &c->record_data;
}
@@ -386,7 +394,7 @@ static struct ctdb_client_call_state *ctdb_client_call_local_send(struct ctdb_db
*(state->call) = *call;
state->ctdb_db = ctdb_db;
- ret = ctdb_call_local(ctdb_db, state->call, header, state, data, true);
+ ret = ctdb_call_local(ctdb_db, state->call, header, state, data, true, ctdb->pnn);
if (ret != 0) {
DEBUG(DEBUG_DEBUG,("ctdb_call_local() failed, ignoring return code %d\n", ret));
}
@@ -4622,3 +4630,41 @@ int ctdb_ctrl_set_db_readonly(struct ctdb_context *ctdb, uint32_t destnode, uint
state = ctdb_ctrl_set_db_readonly_send(ctdb, destnode, dbid);
return ctdb_ctrl_set_db_readonly_recv(ctdb, state);
}
+
+/*
+ set a database to be sticky
+ */
+struct ctdb_client_control_state *
+ctdb_ctrl_set_db_sticky_send(struct ctdb_context *ctdb, uint32_t destnode, uint32_t dbid)
+{
+ TDB_DATA data;
+
+ data.dptr = (uint8_t *)&dbid;
+ data.dsize = sizeof(dbid);
+
+ return ctdb_control_send(ctdb, destnode, 0,
+ CTDB_CONTROL_SET_DB_STICKY, 0, data,
+ ctdb, NULL, NULL);
+}
+
+int ctdb_ctrl_set_db_sticky_recv(struct ctdb_context *ctdb, struct ctdb_client_control_state *state)
+{
+ int ret;
+ int32_t res;
+
+ ret = ctdb_control_recv(ctdb, state, ctdb, NULL, &res, NULL);
+ if (ret != 0 || res != 0) {
+ DEBUG(DEBUG_ERR,(__location__ " ctdb_ctrl_set_db_sticky_recv failed ret:%d res:%d\n", ret, res));
+ return -1;
+ }
+
+ return 0;
+}
+
+int ctdb_ctrl_set_db_sticky(struct ctdb_context *ctdb, uint32_t destnode, uint32_t dbid)
+{
+ struct ctdb_client_control_state *state;
+
+ state = ctdb_ctrl_set_db_sticky_send(ctdb, destnode, dbid);
+ return ctdb_ctrl_set_db_sticky_recv(ctdb, state);
+}
diff --git a/common/ctdb_ltdb.c b/common/ctdb_ltdb.c
index 565a899..3a184bb 100644
--- a/common/ctdb_ltdb.c
+++ b/common/ctdb_ltdb.c
@@ -67,6 +67,7 @@ static void ltdb_initial_header(struct ctdb_db_context *ctdb_db,
/* initial dmaster is the lmaster */
header->dmaster = ctdb_lmaster(ctdb_db->ctdb, &key);
header->flags = CTDB_REC_FLAG_AUTOMATIC;
+ header->laccessor = header->dmaster;
}
diff --git a/doc/ctdbd.1 b/doc/ctdbd.1
index 2c1b979..87f0bfa 100644
--- a/doc/ctdbd.1
+++ b/doc/ctdbd.1
@@ -1,371 +1,462 @@
-.\" ** You probably do not want to edit this file directly **
-.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
-.\" Instead of manually editing it, you probably should edit the DocBook XML
-.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "CTDBD" "1" "12/14/2011" "ctdb" "CTDB \- clustered TDB database"
+'\" t
+.\" Title: ctdbd
+.\" Author: [FIXME: author] [see http://docbook.sf.net/el/author]
+.\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/>
+.\" Date: 03/20/2012
+.\" Manual: CTDB - clustered TDB database
+.\" Source: ctdb
+.\" Language: English
+.\"
+.TH "CTDBD" "1" "03/20/2012" "ctdb" "CTDB \- clustered TDB database"
+.\" -----------------------------------------------------------------
+.\" * Define some portability stuff
+.\" -----------------------------------------------------------------
+.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+.\" http://bugs.debian.org/507673
+.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
+.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.\" -----------------------------------------------------------------
+.\" * set default formatting
+.\" -----------------------------------------------------------------
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
+.\" -----------------------------------------------------------------
+.\" * MAIN CONTENT STARTS HERE *
+.\" -----------------------------------------------------------------
.SH "NAME"
ctdbd \- The CTDB cluster daemon
.SH "SYNOPSIS"
-.HP 6
+.HP \w'\fBctdbd\fR\ 'u
\fBctdbd\fR
-.HP 6
+.HP \w'\fBctdbd\fR\ 'u
\fBctdbd\fR [\-?\ \-\-help] [\-d\ \-\-debug=<INTEGER>] {\-\-dbdir=<directory>} {\-\-dbdir\-persistent=<directory>} [\-\-event\-script\-dir=<directory>] [\-i\ \-\-interactive] [\-\-listen=<address>] [\-\-logfile=<filename>] [\-\-lvs] {\-\-nlist=<filename>} [\-\-no\-lmaster] [\-\-no\-recmaster] [\-\-nosetsched] {\-\-notification\-script=<filename>} [\-\-public\-addresses=<filename>] [\-\-public\-interface=<interface>] {\-\-reclock=<filename>} [\-\-single\-public\-ip=<address>] [\-\-socket=<filename>] [\-\-start\-as\-disabled] [\-\-start\-as\-stopped] [\-\-syslog] [\-\-log\-ringbuf\-size=<num\-entries>] [\-\-torture] [\-\-transport=<STRING>] [\-\-usage]
.SH "DESCRIPTION"
.PP
-ctdbd is the main ctdb daemon.
+ctdbd is the main ctdb daemon\&.
.PP
-ctdbd provides a clustered version of the TDB database with automatic rebuild/recovery of the databases upon nodefailures.
+ctdbd provides a clustered version of the TDB database with automatic rebuild/recovery of the databases upon nodefailures\&.
.PP
-Combined with a cluster filesystem ctdbd provides a full HA environment for services such as clustered Samba and NFS as well as other services.
+Combined with a cluster filesystem ctdbd provides a full HA environment for services such as clustered Samba and NFS as well as other services\&.
.PP
-ctdbd provides monitoring of all nodes in the cluster and automatically reconfigures the cluster and recovers upon node failures.
+ctdbd provides monitoring of all nodes in the cluster and automatically reconfigures the cluster and recovers upon node failures\&.
.PP
-ctdbd is the main component in clustered Samba that provides a high\-availability load\-sharing CIFS server cluster.
+ctdbd is the main component in clustered Samba that provides a high\-availability load\-sharing CIFS server cluster\&.
.SH "OPTIONS"
-.TP
+.PP
\-? \-\-help
-Print some help text to the screen.
-.TP
+.RS 4
+Print some help text to the screen\&.
+.RE
+.PP
\-d \-\-debug=<DEBUGLEVEL>
-This option sets the debuglevel on the ctdbd daemon which controls what will be written to the logfile. The default is 0 which will only log important events and errors. A larger number will provide additional logging.
-.TP
+.RS 4
+This option sets the debuglevel on the ctdbd daemon which controls what will be written to the logfile\&. The default is 0 which will only log important events and errors\&. A larger number will provide additional logging\&.
+.RE
+.PP
\-\-dbdir=<directory>
-This is the directory on local storage where ctdbd keeps the local copy of the TDB databases. This directory is local for each node and should not be stored on the shared cluster filesystem.
+.RS 4
+This is the directory on local storage where ctdbd keeps the local copy of the TDB databases\&. This directory is local for each node and should not be stored on the shared cluster filesystem\&.
.sp
-This directory would usually be /var/ctdb .
-.TP
+This directory would usually be /var/ctdb \&.
+.RE
+.PP
\-\-dbdir\-persistent=<directory>
-This is the directory on local storage where ctdbd keeps the local copy of the persistent TDB databases. This directory is local for each node and should not be stored on the shared cluster filesystem.
+.RS 4
+This is the directory on local storage where ctdbd keeps the local copy of the persistent TDB databases\&. This directory is local for each node and should not be stored on the shared cluster filesystem\&.
.sp
-This directory would usually be /etc/ctdb/persistent .
-.TP
+This directory would usually be /etc/ctdb/persistent \&.
+.RE
+.PP
\-\-event\-script\-dir=<directory>
-This option is used to specify the directory where the CTDB event scripts are stored.
+.RS 4
+This option is used to specify the directory where the CTDB event scripts are stored\&.
.sp
-This will normally be /etc/ctdb/events.d which is part of the ctdb distribution.
-.TP
+This will normally be /etc/ctdb/events\&.d which is part of the ctdb distribution\&.
+.RE
+.PP
\-i \-\-interactive
-By default ctdbd will detach itself from the shell and run in the background as a daemon. This option makes ctdbd to start in interactive mode.
-.TP
+.RS 4
+By default ctdbd will detach itself from the shell and run in the background as a daemon\&. This option makes ctdbd to start in interactive mode\&.
+.RE
+.PP
\-\-listen=<address>
-This specifies which ip address ctdb will bind to. By default ctdbd will bind to the first address it finds in the /etc/ctdb/nodes file and which is also present on the local system in which case you do not need to provide this option.
+.RS 4
+This specifies which ip address ctdb will bind to\&. By default ctdbd will bind to the first address it finds in the /etc/ctdb/nodes file and which is also present on the local system in which case you do not need to provide this option\&.
.sp
-This option is only required when you want to run multiple ctdbd daemons/nodes on the same physical host in which case there would be multiple entries in /etc/ctdb/nodes what would match a local interface.
-.TP
+This option is only required when you want to run multiple ctdbd daemons/nodes on the same physical host in which case there would be multiple entries in /etc/ctdb/nodes what would match a local interface\&.
+.RE
+.PP
\-\-logfile=<filename>
-This is the file where ctdbd will write its log. This is usually /var/log/log.ctdb .
-.TP
+.RS 4
+This is the file where ctdbd will write its log\&. This is usually /var/log/log\&.ctdb \&.
+.RE
+.PP
\-\-lvs
-This option is used to activate the LVS capability on a CTDB node. Please see the LVS section.
-.TP
+.RS 4
+This option is used to activate the LVS capability on a CTDB node\&. Please see the LVS section\&.
+.RE
+.PP
\-\-nlist=<filename>
-This file contains a list of the private ip addresses of every node in the cluster. There is one line/ip address for each node. This file must be the same for all nodes in the cluster.
+.RS 4
+This file contains a list of the private ip addresses of every node in the cluster\&. There is one line/ip address for each node\&. This file must be the same for all nodes in the cluster\&.
.sp
-This file is usually /etc/ctdb/nodes .
-.TP
+This file is usually /etc/ctdb/nodes \&.
+.RE
+.PP
\-\-no\-lmaster
-This argument specifies that this node can NOT become an lmaster for records in the database. This means that it will never show up in the vnnmap. This feature is primarily used for making a cluster span across a WAN link and use CTDB as a WAN\-accelerator.
+.RS 4
+This argument specifies that this node can NOT become an lmaster for records in the database\&. This means that it will never show up in the vnnmap\&. This feature is primarily used for making a cluster span across a WAN link and use CTDB as a WAN\-accelerator\&.
.sp
-Please see the "remote cluster nodes" section for more information.
-.TP
+Please see the "remote cluster nodes" section for more information\&.
+.RE
+.PP
\-\-no\-recmaster
-This argument specifies that this node can NOT become a recmaster for the database. This feature is primarily used for making a cluster span across a WAN link and use CTDB as a WAN\-accelerator.
+.RS 4
+This argument specifies that this node can NOT become a recmaster for the database\&. This feature is primarily used for making a cluster span across a WAN link and use CTDB as a WAN\-accelerator\&.
.sp
-Please see the "remote cluster nodes" section for more information.
-.TP
+Please see the "remote cluster nodes" section for more information\&.
+.RE
+.PP
\-\-nosetsched
-This is a ctdbd debugging option. this option is only used when debugging ctdbd.
+.RS 4
+This is a ctdbd debugging option\&. this option is only used when debugging ctdbd\&.
.sp
-Normally ctdb will change its scheduler to run as a real\-time process. This is the default mode for a normal ctdbd operation to gurarantee that ctdbd always gets the cpu cycles that it needs.
+Normally ctdb will change its scheduler to run as a real\-time process\&. This is the default mode for a normal ctdbd operation to gurarantee that ctdbd always gets the cpu cycles that it needs\&.
.sp
-This option is used to tell ctdbd to NOT run as a real\-time process and instead run ctdbd as a normal userspace process. This is useful for debugging and when you want to run ctdbd under valgrind or gdb. (You don't want to attach valgrind or gdb to a real\-time process.)
-.TP
+This option is used to tell ctdbd to NOT run as a real\-time process and instead run ctdbd as a normal userspace process\&. This is useful for debugging and when you want to run ctdbd under valgrind or gdb\&. (You don\*(Aqt want to attach valgrind or gdb to a real\-time process\&.)
+.RE
+.PP
\-\-notification\-script=<filename>
-This specifies a script which will be invoked by ctdb when certain state changes occur in ctdbd and when you may want to trigger this to run certain scripts.
+.RS 4
+This specifies a script which will be invoked by ctdb when certain state changes occur in ctdbd and when you may want to trigger this to run certain scripts\&.
.sp
-This file is usually /etc/ctdb/notify.sh .
+This file is usually /etc/ctdb/notify\&.sh \&.
.sp
-See the NOTIFICATION SCRIPT section below for more information.
-.TP
+See the NOTIFICATION SCRIPT section below for more information\&.
+.RE
+.PP
\-\-public_addresses=<filename>
-When used with IP takeover this specifies a file containing the public ip addresses to use on the cluster. This file contains a list of ip addresses netmasks and interfaces. When ctdb is operational it will distribute these public ip addresses evenly across the available nodes.
+.RS 4
+When used with IP takeover this specifies a file containing the public ip addresses to use on the cluster\&. This file contains a list of ip addresses netmasks and interfaces\&. When ctdb is operational it will distribute these public ip addresses evenly across the available nodes\&.
.sp
This is usually the file /etc/ctdb/public_addresses
-.TP
+.RE
+.PP
\-\-public\-interface=<interface>
-This option tells ctdb which interface to attach public\-addresses to and also where to attach the single\-public\-ip when used.
+.RS 4
+This option tells ctdb which interface to attach public\-addresses to and also where to attach the single\-public\-ip when used\&.
.sp
-This is only required when using public ip addresses and only when you don't specify the interface explicitly in /etc/ctdb/public_addresses or when you are using \-\-single\-public\-ip.
+This is only required when using public ip addresses and only when you don\*(Aqt specify the interface explicitly in /etc/ctdb/public_addresses or when you are using \-\-single\-public\-ip\&.
.sp
-If you omit this argument when using public addresses or single public ip, ctdb will not be able to send out Gratious ARPs correctly or be able to kill tcp connections correctly which will lead to application failures.
-.TP
+If you omit this argument when using public addresses or single public ip, ctdb will not be able to send out Gratious ARPs correctly or be able to kill tcp connections correctly which will lead to application failures\&.
+.RE
+.PP
\-\-reclock=<filename>
-This is the name of the lock file stored of the shared cluster filesystem that ctdbd uses to prevent split brains from occuring. This file must be stored on shared storage.
+.RS 4
+This is the name of the lock file stored of the shared cluster filesystem that ctdbd uses to prevent split brains from occuring\&. This file must be stored on shared storage\&.
.sp
-It is possible to run CTDB without a reclock file, but then there will be no protection against split brain if the network becomes partitioned. Using CTDB without a reclock file is strongly discouraged.
-.TP
+It is possible to run CTDB without a reclock file, but then there will be no protection against split brain if the network becomes partitioned\&. Using CTDB without a reclock file is strongly discouraged\&.
+.RE
+.PP
\-\-socket=<filename>
-This specifies the name of the domain socket that ctdbd will create. This socket is used for local clients to attach to and communicate with the ctdbd daemon.
+.RS 4
+This specifies the name of the domain socket that ctdbd will create\&. This socket is used for local clients to attach to and communicate with the ctdbd daemon\&.
.sp
-The default is /tmp/ctdb.socket . You only need to use this option if you plan to run multiple ctdbd daemons on the same physical host.
-.TP
+The default is /tmp/ctdb\&.socket \&. You only need to use this option if you plan to run multiple ctdbd daemons on the same physical host\&.
+.RE
+.PP
\-\-start\-as\-disabled
-This makes the ctdb daemon to be DISABLED when it starts up.
+.RS 4
+This makes the ctdb daemon to be DISABLED when it starts up\&.
.sp
-As it is DISABLED it will not get any of the public ip addresses allocated to it, and thus this allow you to start ctdb on a node without causing any ip address to failover from other nodes onto the new node.
+As it is DISABLED it will not get any of the public ip addresses allocated to it, and thus this allow you to start ctdb on a node without causing any ip address to failover from other nodes onto the new node\&.
.sp
-When used, the administrator must keep track of when nodes start and manually enable them again using the "ctdb enable" command, or else the node will not host any services.
+When used, the administrator must keep track of when nodes start and manually enable them again using the "ctdb enable" command, or else the node will not host any services\&.
.sp
-A node that is DISABLED will not host any services and will not be reachable/used by any clients.
-.TP
+A node that is DISABLED will not host any services and will not be reachable/used by any clients\&.
+.RE
+.PP
\-\-start\-as\-stopped
-This makes the ctdb daemon to be STOPPED when it starts up.
+.RS 4
+This makes the ctdb daemon to be STOPPED when it starts up\&.
.sp
-A node that is STOPPED does not host any public addresses. It is not part of the VNNMAP so it does act as an LMASTER. It also has all databases locked in recovery mode until restarted.
+A node that is STOPPED does not host any public addresses\&. It is not part of the VNNMAP so it does act as an LMASTER\&. It also has all databases locked in recovery mode until restarted\&.
.sp
-To restart and activate a STOPPED node, the command "ctdb continue" is used.
+To restart and activate a STOPPED node, the command "ctdb continue" is used\&.
.sp
-A node that is STOPPED will not host any services and will not be reachable/used by any clients.
-.TP
+A node that is STOPPED will not host any services and will not be reachable/used by any clients\&.
+.RE
+.PP
\-\-syslog
-Send all log messages to syslog instead of to the ctdb logfile.
-.TP
+.RS 4
+Send all log messages to syslog instead of to the ctdb logfile\&.
+.RE
+.PP
\-\-log\-ringbuf\-size=<num\-entries>
-In addition to the normal loggign to a log file, CTDBD also keeps a in\-memory ringbuffer containing the most recent log entries for all log levels (except DEBUG).
+.RS 4
+In addition to the normal loggign to a log file, CTDBD also keeps a in\-memory ringbuffer containing the most recent log entries for all log levels (except DEBUG)\&.
.sp
-This is useful since it allows for keeping continuous logs to a file at a reasonable non\-verbose level, but shortly after an incident has occured, a much more detailed log can be pulled from memory. This can allow you to avoid having to reproduce an issue due to the on\-disk logs being of insufficient detail.
+This is useful since it allows for keeping continuous logs to a file at a reasonable non\-verbose level, but shortly after an incident has occured, a much more detailed log can be pulled from memory\&. This can allow you to avoid having to reproduce an issue due to the on\-disk logs being of insufficient detail\&.
.sp
-This in\-memory ringbuffer contains a fixed number of the most recent entries. This is settable at startup either through the \-\-log\-ringbuf\-size argument, or preferably by using CTDB_LOG_RINGBUF_SIZE in the sysconfig file.
+This in\-memory ringbuffer contains a fixed number of the most recent entries\&. This is settable at startup either through the \-\-log\-ringbuf\-size argument, or preferably by using CTDB_LOG_RINGBUF_SIZE in the sysconfig file\&.
.sp
-Use the "ctdb getlog" command to access this log.
-.TP
+Use the "ctdb getlog" command to access this log\&.
+.RE
+.PP
\-\-torture
-This option is only used for development and testing of ctdbd. It adds artificial errors and failures to the common codepaths in ctdbd to verify that ctdbd can recover correctly for failures.
+.RS 4
+This option is only used for development and testing of ctdbd\&. It adds artificial errors and failures to the common codepaths in ctdbd to verify that ctdbd can recover correctly for failures\&.
.sp
-You do NOT want to use this option unless you are developing and testing new functionality in ctdbd.
-.TP
+You do NOT want to use this option unless you are developing and testing new functionality in ctdbd\&.
+.RE
+.PP
\-\-transport=<STRING>
-This option specifies which transport to use for ctdbd internode communications. The default is "tcp".
+.RS 4
+This option specifies which transport to use for ctdbd internode communications\&. The default is "tcp"\&.
.sp
-Currently only "tcp" is supported but "infiniband" might be implemented in the future.
-.TP
+Currently only "tcp" is supported but "infiniband" might be implemented in the future\&.
+.RE
+.PP
\-\-usage
-Print useage information to the screen.
+.RS 4
+Print useage information to the screen\&.
+.RE
.SH "PRIVATE VS PUBLIC ADDRESSES"
.PP
-When used for ip takeover in a HA environment, each node in a ctdb cluster has multiple ip addresses assigned to it. One private and one or more public.
+When used for ip takeover in a HA environment, each node in a ctdb cluster has multiple ip addresses assigned to it\&. One private and one or more public\&.
.SS "Private address"
.PP
-This is the physical ip address of the node which is configured in linux and attached to a physical interface. This address uniquely identifies a physical node in the cluster and is the ip addresses that ctdbd will use to communicate with the ctdbd daemons on the other nodes in the cluster.
+This is the physical ip address of the node which is configured in linux and attached to a physical interface\&. This address uniquely identifies a physical node in the cluster and is the ip addresses that ctdbd will use to communicate with the ctdbd daemons on the other nodes in the cluster\&.
.PP
-The private addresses are configured in /etc/ctdb/nodes (unless the \-\-nlist option is used) and contain one line for each node in the cluster. Each line contains the private ip address for one node in the cluster. This file must be the same on all nodes in the cluster.
+The private addresses are configured in /etc/ctdb/nodes (unless the \-\-nlist option is used) and contain one line for each node in the cluster\&. Each line contains the private ip address for one node in the cluster\&. This file must be the same on all nodes in the cluster\&.
.PP
-Since the private addresses are only available to the network when the corresponding node is up and running you should not use these addresses for clients to connect to services provided by the cluster. Instead client applications should only attach to the public addresses since these are guaranteed to always be available.
+Since the private addresses are only available to the network when the corresponding node is up and running you should not use these addresses for clients to connect to services provided by the cluster\&. Instead client applications should only attach to the public addresses since these are guaranteed to always be available\&.
.PP
-When using ip takeover, it is strongly recommended that the private addresses are configured on a private network physically separated from the rest of the network and that this private network is dedicated to CTDB traffic.
+When using ip takeover, it is strongly recommended that the private addresses are configured on a private network physically separated from the rest of the network and that this private network is dedicated to CTDB traffic\&.
Example /etc/ctdb/nodes for a four node cluster:
- .sp
+
+.sp
+.if n \{\
+.RS 4
+.\}
.nf
- 10.1.1.1
- 10.1.1.2
- 10.1.1.3
- 10.1.1.4
+ 10\&.1\&.1\&.1
+ 10\&.1\&.1\&.2
+ 10\&.1\&.1\&.3
+ 10\&.1\&.1\&.4
.fi
+.if n \{\
+.RE
+.\}
.SS "Public address"
.PP
-A public address on the other hand is not attached to an interface. This address is managed by ctdbd itself and is attached/detached to a physical node at runtime.
+A public address on the other hand is not attached to an interface\&. This address is managed by ctdbd itself and is attached/detached to a physical node at runtime\&.
.PP
-The ctdb cluster will assign/reassign these public addresses across the available healthy nodes in the cluster. When one node fails, its public address will be migrated to and taken over by a different node in the cluster to ensure that all public addresses are always available to clients as long as there are still nodes available capable of hosting this address.
+The ctdb cluster will assign/reassign these public addresses across the available healthy nodes in the cluster\&. When one node fails, its public address will be migrated to and taken over by a different node in the cluster to ensure that all public addresses are always available to clients as long as there are still nodes available capable of hosting this address\&.
.PP
-These addresses are not physically attached to a specific node. The 'ctdb ip' command can be used to view the current assignment of public addresses and which physical node is currently serving it.
+These addresses are not physically attached to a specific node\&. The \*(Aqctdb ip\*(Aq command can be used to view the current assignment of public addresses and which physical node is currently serving it\&.
.PP
-On each node this file contains a list of the public addresses that this node is capable of hosting. The list also contain the netmask and the interface where this address should be attached for the case where you may want to serve data out through multiple different interfaces.
+On each node this file contains a list of the public addresses that this node is capable of hosting\&. The list also contain the netmask and the interface where this address should be attached for the case where you may want to serve data out through multiple different interfaces\&.
Example /etc/ctdb/public_addresses for a node that can host 4 public addresses:
- .sp
+
+.sp
+.if n \{\
+.RS 4
+.\}
.nf
- 11.1.1.1/24 eth0
- 11.1.1.2/24 eth0
- 11.1.2.1/24 eth1
- 11.1.2.2/24 eth1
+ 11\&.1\&.1\&.1/24 eth0
+ 11\&.1\&.1\&.2/24 eth0
+ 11\&.1\&.2\&.1/24 eth1
+ 11\&.1\&.2\&.2/24 eth1
.fi
+.if n \{\
+.RE
+.\}
.PP
-In most cases this file would be the same on all nodes in a cluster but there are exceptions when one may want to use different files on different nodes.
+In most cases this file would be the same on all nodes in a cluster but there are exceptions when one may want to use different files on different nodes\&.
Example: 4 nodes partitioned into two subgroups :
- .sp
+
+.sp
+.if n \{\
+.RS 4
+.\}
.nf
Node 0:/etc/ctdb/public_addresses
--
CTDB repository
More information about the samba-cvs
mailing list