The branch, master has been updated
via 3f471da605b9c43d5e1206452f238c2a91dc02f7 (commit)
via 8fc71ad4da746e28406c06a95928052b29803062 (commit)
from faf25e8a2fdf80a016048e1f698a014ceb5e604f (commit)
http://gitweb.samba.org/?p=ctdb.git;a=shortlog;h=master
- Log -----------------------------------------------------------------
commit 3f471da605b9c43d5e1206452f238c2a91dc02f7
Author: Ronnie Sahlberg <[email protected]>
Date: Wed Dec 14 14:23:53 2011 +1100
DOC: Update the manpage to describe all relevant tunables
commit 8fc71ad4da746e28406c06a95928052b29803062
Author: Ronnie Sahlberg <[email protected]>
Date: Wed Dec 14 12:52:35 2011 +1100
typo
-----------------------------------------------------------------------
Summary of changes:
doc/ctdb.1 | 2 +-
doc/ctdbd.1 | 148 ++++++++++++++++++++++--
doc/ctdbd.1.html | 266 +++++++++++++++++++++++++++++++++-----------
doc/ctdbd.1.xml | 320 ++++++++++++++++++++++++++++++++++++++++++++++++----
server/ctdb_call.c | 2 +-
5 files changed, 638 insertions(+), 100 deletions(-)
Changeset truncated at 500 lines:
diff --git a/doc/ctdb.1 b/doc/ctdb.1
index 70405d0..ab481fb 100644
--- a/doc/ctdb.1
+++ b/doc/ctdb.1
@@ -2,7 +2,7 @@
.\" 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 "CTDB" "1" "11/30/2011" "ctdb" "CTDB \- clustered TDB database"
+.TH "CTDB" "1" "12/14/2011" "ctdb" "CTDB \- clustered TDB database"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
diff --git a/doc/ctdbd.1 b/doc/ctdbd.1
index 40044d4..2c1b979 100644
--- a/doc/ctdbd.1
+++ b/doc/ctdbd.1
@@ -2,7 +2,7 @@
.\" 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" "11/30/2011" "ctdb" "CTDB \- clustered TDB database"
+.TH "CTDBD" "1" "12/14/2011" "ctdb" "CTDB \- clustered TDB database"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
@@ -243,16 +243,62 @@ STOPPED \- A node that is stopped does not host any
public ip addresses, nor is
.SH "PUBLIC TUNABLES"
.PP
These are the public tuneables that can be used to control how ctdb behaves.
+.SS "MaxRedirectCount"
+.PP
+Default: 3
+.PP
+If we are not the DMASTER and need to fetch a record across the network we
first send the request to the LMASTER after which the record is passed onto the
current DMASTER. If the DMASTER changes before the request has reached that
node, the request will be passed onto the "next" DMASTER. For very hot records
that migrate rapidly across the cluster this can cause a request to "chase" the
record for many hops before it catches up with the record. this is how many
hops we allow trying to chase the DMASTER before we switch back to the LMASTER
again to ask for new directions.
+.PP
+When chasing a record, this is how many hops we will chase the record for
before going back to the LMASTER to ask for new guidance.
+.SS "SeqnumInterval"
+.PP
+Default: 1000
+.PP
+Some databases have seqnum tracking enabled, so that samba will be able to
detect asynchronously when there has been updates to the database. Everytime a
database is updated its sequence number is increased.
+.PP
+This tunable is used to specify in 'ms' how frequently ctdb will send out
updates to remote nodes to inform them that the sequence number is increased.
+.SS "ControlTimeout"
+.PP
+Default: 60
+.PP
+This is the default setting for timeout for when sending a control message to
either the local or a remote ctdb daemon.
+.SS "TraverseTimeout"
+.PP
+Default: 20
+.PP
+This setting controls how long we allow a traverse process to run. After this
timeout triggers, the main ctdb daemon will abort the traverse if it has not
yet finished.
.SS "KeepaliveInterval"
.PP
-Default: 1
+Default: 5
.PP
-How often should the nodes send keepalives to eachother.
+How often in seconds should the nodes send keepalives to eachother.
.SS "KeepaliveLimit"
.PP
Default: 5
.PP
After how many keepalive intervals without any traffic should a node wait
until marking the peer as DISCONNECTED.
+.PP
+If a node has hung, it can thus take KeepaliveInterval*(KeepaliveLimit+1)
seconds before we determine that the node is DISCONNECTED and that we require a
recovery. This limitshould not be set too high since we want a hung node to be
detectec, and expunged from the cluster well before common CIFS timeouts
(45\-90 seconds) kick in.
+.SS "RecoverTimeout"
+.PP
+Default: 20
+.PP
+This is the default setting for timeouts for controls when sent from the
recovery daemon. We allow longer control timeouts from the recovery daemon than
from normal use since the recovery dameon often use controls that can take a
lot longer than normal controls.
+.SS "RecoverInterval"
+.PP
+Default: 1
+.PP
+How frequently in seconds should the recovery daemon perform the consistency
checks that determine if we need to perform a recovery or not.
+.SS "ElectionTimeout"
+.PP
+Default: 3
+.PP
+When electing a new recovery master, this is how many seconds we allow the
election to take before we either deem the election finished or we fail the
election and start a new one.
+.SS "TakeoverTimeout"
+.PP
+Default: 9
+.PP
+This is how many seconds we allow controls to take for IP failover events.
.SS "MonitorInterval"
.PP
Default: 15
@@ -268,6 +314,21 @@ How often will ctdb record and store the "tickle"
information used to kickstart
Default: 20
.PP
How long should ctdb let an event script run before aborting it and marking
the node unhealthy.
+.SS "EventScriptTimeoutCount"
+.PP
+Default: 1
+.PP
+How many events in a row needs to timeout before we flag the node UNHEALTHY.
This setting is useful if your scripts can not be written so that they do not
hang for benign reasons.
+.SS "EventScriptUnhealthyOnTimeout"
+.PP
+Default: 0
+.PP
+This setting can be be used to make ctdb never become UNHEALTHY if your
eventscripts keep hanging/timing out.
+.SS "RecoveryGracePeriod"
+.PP
+Default: 120
+.PP
+During recoveries, if a node has not caused recovery failures during the last
grace period, any records of transgressions that the node has caused recovery
failures will be forgiven. This resets the ban\-counter back to zero for that
node.
.SS "RecoveryBanPeriod"
.PP
Default: 300
@@ -275,9 +336,14 @@ Default: 300
If a node becomes banned causing repetitive recovery failures. The node will
eventually become banned from the cluster. This controls how long the culprit
node will be banned from the cluster before it is allowed to try to join the
cluster again. Don't set to small. A node gets banned for a reason and it is
usually due to real problems with the node.
.SS "DatabaseHashSize"
.PP
-Default: 100000
+Default: 100001
.PP
Size of the hash chains for the local store of the tdbs that ctdb manages.
+.SS "DatabaseMaxDead"
+.PP
+Default: 5
+.PP
+How many dead records per hashchain in the TDB database do we allow before the
freelist needs to be processed.
.SS "RerecoveryTimeout"
.PP
Default: 10
@@ -287,21 +353,24 @@ Once a recovery has completed, no additional recoveries
are permitted until this
.PP
Default: 1
.PP
-When set to 0, this disables BANNING completely in the cluster and thus nodes
can not get banned, even it they break. Don't set to 0.
+When set to 0, this disables BANNING completely in the cluster and thus nodes
can not get banned, even it they break. Don't set to 0 unless you know what you
are doing.
.SS "DeterministicIPs"
.PP
-Default: 1
+Default: 0
.PP
When enabled, this tunable makes ctdb try to keep public IP addresses locked
to specific nodes as far as possible. This makes it easier for debugging since
you can know that as long as all nodes are healthy public IP X will always be
hosted by node Y.
.PP
The cost of using deterministic IP address assignment is that it disables part
of the logic where ctdb tries to reduce the number of public IP assignment
changes in the cluster. This tunable may increase the number of IP
failover/failbacks that are performed on the cluster by a small margin.
-.SS "DisableWhenUnhealthy"
+.SS "LCP2PublicIPs"
.PP
-Default: 0
+Default: 1
.PP
-When set, As soon as a node becomes unhealthy, that node will also
automatically become permanently DISABLED. Once a node is DISABLED, the only
way to make it participate in the cluster again and host services is by
manually enabling the node again using 'ctdb enable'.
+When enabled this switches ctdb to use the LCP2 ip allocation algorithm.
+.SS "ReclockPingPeriod"
.PP
-This disables parts of the resilience and robustness of the cluster and should
ONLY be used when the system administrator is actively monitoring the cluster,
so that nodes can be enabled again.
+Default: x
+.PP
+Obsolete
.SS "NoIPFailback"
.PP
Default: 0
@@ -311,6 +380,65 @@ When set to 1, ctdb will not perform failback of IP
addresses when a node become
Use with caution! Normally when a node becomes available to the cluster ctdb
will try to reassign public IP addresses onto the new node as a way to
distribute the workload evenly across the clusternode. Ctdb tries to make sure
that all running nodes have approximately the same number of public addresses
it hosts.
.PP
When you enable this tunable, CTDB will no longer attempt to rebalance the
cluster by failing IP addresses back to the new nodes. An unbalanced cluster
will therefore remain unbalanced until there is manual intervention from the
administrator. When this parameter is set, you can manually fail public IP
addresses over to the new node(s) using the 'ctdb moveip' command.
+.SS "DisableIPFailover"
+.PP
+Default: 0
+.PP
+When enabled, ctdb weill not perform failover or failback. Even if a node
fails while holding public IPs, ctdb will not recover the IPs or assign them to
another node.
+.PP
+When you enable this tunable, CTDB will no longer attempt to recover the
cluster by failing IP addresses over to other nodes. This leads to a service
outage until the administrator has manually performed failover to replacement
nodes using the 'ctdb moveip' command.
+.SS "VerboseMemoryNames"
+.PP
+Default: 0
+.PP
+This feature consumes additional memory. when used the talloc library will
create more verbose names for all talloc allocated objects.
+.SS "RecdPingTimeout"
+.PP
+Default: 60
+.PP
+If the main dameon has not heard a "ping" from the recovery dameon for this
many seconds, the main dameon will log a message that the recovery daemon is
potentially hung.
+.SS "RecdFailCount"
+.PP
+Default: 10
+.PP
+If the recovery daemon has failed to ping the main dameon for this many
consecutive intervals, the main daemon will consider the recovery daemon as
hung and will try to restart it to recover.
+.SS "LogLatencyMs"
+.PP
+Default: 0
+.PP
+When set to non\-zero, this will make the main daemon log any operation that
took longer than this value, in 'ms', to complete. These include "how long time
a lockwait child process needed", "how long time to write to a persistent
database" but also "how long did it take to get a response to a CALL from a
remote node".
+.SS "RecLockLatencyMs"
+.PP
+Default: 1000
+.PP
+When using a reclock file for split brain prevention, if set to non\-zero this
tunable will make the recovery dameon log a message if the fcntl() call to
lock/testlock the recovery file takes longer than this number of ms.
+.SS "RecoveryDropAllIPs"
+.PP
+Default: 120
+.PP
+If we have been stuck in recovery, or stopped, or banned, mode for this many
seconds we will force drop all held public addresses.
+.SS "verifyRecoveryLock"
+.PP
+Default: 1
+.PP
+Should we take a fcntl() lock on the reclock file to verify that we are the
sole recovery master node on the cluster or not.
+.SS "DeferredAttachTO"
+.PP
+Default: 120
+.PP
+When databases are frozen we do not allow clients to attach to the databases.
Instead of returning an error immediately to the application the attach request
from the client is deferred until the database becomes available again at which
stage we respond to the client.
+.PP
+This timeout controls how long we will defer the request from the client
before timing it out and returning an error to the client.
+.SS "StatHistoryInterval"
+.PP
+Default: 1
+.PP
+Granularity of the statistics collected in the statistics history.
+.SS "AllowClientDBAttach"
+.PP
+Default: 1
+.PP
+When set to 0, clients are not allowed to attach to any databases. This can be
used to temporarily block any new processes from attaching to and accessing the
databases.
.SS "RecoverPDBBySeqNum"
.PP
Default: 0
diff --git a/doc/ctdbd.1.html b/doc/ctdbd.1.html
index 84bf746..d42952a 100644
--- a/doc/ctdbd.1.html
+++ b/doc/ctdbd.1.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1"><title>ctdbd</title><meta name="generator" content="DocBook
XSL Stylesheets V1.69.1"></head><body bgcolor="white" text="black"
link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry"
lang="en"><a name="ctdbd.1"></a><div class="titlepage"></div><div
class="refnamediv"><h2>Name</h2><p>ctdbd — The CTDB cluster
daemon</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div
class="cmdsynopsis"><p><code class="command">ctdbd</code> </p></div><div
class="cmdsynopsis"><p><code class="command">ctdbd</code> [-? --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&g
t;] [--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]</p></div></div><div class="refsect1"
lang="en"><a name="id1914463"></a><h2>DESCRIPTION</h2><p>
+<html><head><meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1"><title>ctdbd</title><meta name="generator" content="DocBook
XSL Stylesheets V1.69.1"></head><body bgcolor="white" text="black"
link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry"
lang="en"><a name="ctdbd.1"></a><div class="titlepage"></div><div
class="refnamediv"><h2>Name</h2><p>ctdbd — The CTDB cluster
daemon</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div
class="cmdsynopsis"><p><code class="command">ctdbd</code> </p></div><div
class="cmdsynopsis"><p><code class="command">ctdbd</code> [-? --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&g
t;] [--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]</p></div></div><div class="refsect1"
lang="en"><a name="id2840774"></a><h2>DESCRIPTION</h2><p>
ctdbd is the main ctdb daemon.
</p><p>
ctdbd provides a clustered version of the TDB database with automatic
rebuild/recovery of the databases upon nodefailures.
@@ -8,7 +8,7 @@
ctdbd provides monitoring of all nodes in the cluster and automatically
reconfigures the cluster and recovers upon node failures.
</p><p>
ctdbd is the main component in clustered Samba that provides a
high-availability load-sharing CIFS server cluster.
- </p></div><div class="refsect1" lang="en"><a
name="id1914490"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span
class="term">-? --help</span></dt><dd><p>
+ </p></div><div class="refsect1" lang="en"><a
name="id2840801"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span
class="term">-? --help</span></dt><dd><p>
Print some help text to the screen.
</p></dd><dt><span class="term">-d
--debug=<DEBUGLEVEL></span></dt><dd><p>
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.
@@ -154,10 +154,10 @@
implemented in the future.
</p></dd><dt><span class="term">--usage</span></dt><dd><p>
Print useage information to the screen.
- </p></dd></dl></div></div><div class="refsect1" lang="en"><a
name="id1914959"></a><h2>Private vs Public addresses</h2><p>
+ </p></dd></dl></div></div><div class="refsect1" lang="en"><a
name="id2841270"></a><h2>Private vs Public addresses</h2><p>
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.
- </p><div class="refsect2" lang="en"><a name="id1914968"></a><h3>Private
address</h3><p>
+ </p><div class="refsect2" lang="en"><a name="id2841279"></a><h3>Private
address</h3><p>
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
@@ -187,7 +187,7 @@
10.1.1.2
10.1.1.3
10.1.1.4
- </pre></div><div class="refsect2" lang="en"><a
name="id1915004"></a><h3>Public address</h3><p>
+ </pre></div><div class="refsect2" lang="en"><a
name="id2841315"></a><h3>Public address</h3><p>
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.
@@ -248,7 +248,7 @@
unavailable. 10.1.1.1 can not be failed over to node 2 or node 3 since
these nodes do not have this ip address listed in their public
addresses file.
- </p></div></div><div class="refsect1" lang="en"><a
name="id1915065"></a><h2>Node status</h2><p>
+ </p></div></div><div class="refsect1" lang="en"><a
name="id2841375"></a><h2>Node status</h2><p>
The current status of each node in the cluster can be viewed by the
'ctdb status' command.
</p><p>
@@ -285,61 +285,199 @@
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="refsect1" lang="en"><a
name="id1915113"></a><h2>PUBLIC TUNABLES</h2><p>
+ </p></div><div class="refsect1" lang="en"><a
name="id2841424"></a><h2>PUBLIC TUNABLES</h2><p>
These are the public tuneables that can be used to control how ctdb
behaves.
- </p><div class="refsect2" lang="en"><a
name="id1915123"></a><h3>KeepaliveInterval</h3><p>Default: 1</p><p>
- How often should the nodes send keepalives to eachother.
- </p></div><div class="refsect2" lang="en"><a
name="id1915135"></a><h3>KeepaliveLimit</h3><p>Default: 5</p><p>
+ </p><div class="refsect2" lang="en"><a
name="id2841433"></a><h3>MaxRedirectCount</h3><p>Default: 3</p><p>
+ If we are not the DMASTER and need to fetch a record across the network
+ we first send the request to the LMASTER after which the record
+ is passed onto the current DMASTER. If the DMASTER changes before
+ the request has reached that node, the request will be passed onto the
+ "next" DMASTER. For very hot records that migrate rapidly across the
+ cluster this can cause a request to "chase" the record for many hops
+ before it catches up with the record.
+
+ this is how many hops we allow trying to chase the DMASTER before we
+ switch back to the LMASTER again to ask for new directions.
+ </p><p>
+ When chasing a record, this is how many hops we will chase the record
+ for before going back to the LMASTER to ask for new guidance.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841455"></a><h3>SeqnumInterval</h3><p>Default: 1000</p><p>
+ Some databases have seqnum tracking enabled, so that samba will be able
+ to detect asynchronously when there has been updates to the database.
+ Everytime a database is updated its sequence number is increased.
+ </p><p>
+ This tunable is used to specify in 'ms' how frequently ctdb will
+ send out updates to remote nodes to inform them that the sequence
+ number is increased.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841473"></a><h3>ControlTimeout</h3><p>Default: 60</p><p>
+ This is the default
+ setting for timeout for when sending a control message to either the
+ local or a remote ctdb daemon.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841486"></a><h3>TraverseTimeout</h3><p>Default: 20</p><p>
+ This setting controls how long we allow a traverse process to run.
+ After this timeout triggers, the main ctdb daemon will abort the
+ traverse if it has not yet finished.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841500"></a><h3>KeepaliveInterval</h3><p>Default: 5</p><p>
+ How often in seconds should the nodes send keepalives to eachother.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841512"></a><h3>KeepaliveLimit</h3><p>Default: 5</p><p>
After how many keepalive intervals without any traffic should a node
wait until marking the peer as DISCONNECTED.
- </p></div><div class="refsect2" lang="en"><a
name="id1915148"></a><h3>MonitorInterval</h3><p>Default: 15</p><p>
+ </p><p>
+ If a node has hung, it can thus take KeepaliveInterval*(KeepaliveLimit+1)
+ seconds before we determine that the node is DISCONNECTED and that we
+ require a recovery. This limitshould not be set too high since we want
+ a hung node to be detectec, and expunged from the cluster well before
+ common CIFS timeouts (45-90 seconds) kick in.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841532"></a><h3>RecoverTimeout</h3><p>Default: 20</p><p>
+ This is the default setting for timeouts for controls when sent from the
+ recovery daemon. We allow longer control timeouts from the recovery daemon
+ than from normal use since the recovery dameon often use controls that
+ can take a lot longer than normal controls.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841546"></a><h3>RecoverInterval</h3><p>Default: 1</p><p>
+ How frequently in seconds should the recovery daemon perform the
+ consistency checks that determine if we need to perform a recovery or not.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841559"></a><h3>ElectionTimeout</h3><p>Default: 3</p><p>
+ When electing a new recovery master, this is how many seconds we allow
+ the election to take before we either deem the election finished
+ or we fail the election and start a new one.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841572"></a><h3>TakeoverTimeout</h3><p>Default: 9</p><p>
+ This is how many seconds we allow controls to take for IP failover events.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841585"></a><h3>MonitorInterval</h3><p>Default: 15</p><p>
How often should ctdb run the event scripts to check for a nodes health.
- </p></div><div class="refsect2" lang="en"><a
name="id1915161"></a><h3>TickleUpdateInterval</h3><p>Default: 20</p><p>
+ </p></div><div class="refsect2" lang="en"><a
name="id2841598"></a><h3>TickleUpdateInterval</h3><p>Default: 20</p><p>
How often will ctdb record and store the "tickle" information used to
kickstart stalled tcp connections after a recovery.
- </p></div><div class="refsect2" lang="en"><a
name="id1915174"></a><h3>EventScriptTimeout</h3><p>Default: 20</p><p>
+ </p></div><div class="refsect2" lang="en"><a
name="id2841610"></a><h3>EventScriptTimeout</h3><p>Default: 20</p><p>
How long should ctdb let an event script run before aborting it and
marking the node unhealthy.
- </p></div><div class="refsect2" lang="en"><a
name="id1915186"></a><h3>RecoveryBanPeriod</h3><p>Default: 300</p><p>
+ </p></div><div class="refsect2" lang="en"><a
name="id2841623"></a><h3>EventScriptTimeoutCount</h3><p>Default: 1</p><p>
+ How many events in a row needs to timeout before we flag the node
UNHEALTHY.
+ This setting is useful if your scripts can not be written so that they
+ do not hang for benign reasons.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841637"></a><h3>EventScriptUnhealthyOnTimeout</h3><p>Default: 0</p><p>
+ This setting can be be used to make ctdb never become UNHEALTHY if your
+ eventscripts keep hanging/timing out.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841650"></a><h3>RecoveryGracePeriod</h3><p>Default: 120</p><p>
+ During recoveries, if a node has not caused recovery failures during the
+ last grace period, any records of transgressions that the node has caused
+ recovery failures will be forgiven. This resets the ban-counter back to
+ zero for that node.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841664"></a><h3>RecoveryBanPeriod</h3><p>Default: 300</p><p>
If a node becomes banned causing repetitive recovery failures. The node
will
eventually become banned from the cluster.
This controls how long the culprit node will be banned from the cluster
before it is allowed to try to join the cluster again.
Don't set to small. A node gets banned for a reason and it is usually due
to real problems with the node.
- </p></div><div class="refsect2" lang="en"><a
name="id1915201"></a><h3>DatabaseHashSize</h3><p>Default: 100000</p><p>
+ </p></div><div class="refsect2" lang="en"><a
name="id2841682"></a><h3>DatabaseHashSize</h3><p>Default: 100001</p><p>
Size of the hash chains for the local store of the tdbs that ctdb manages.
- </p></div><div class="refsect2" lang="en"><a
name="id1915214"></a><h3>RerecoveryTimeout</h3><p>Default: 10</p><p>
- Once a recovery has completed, no additional recoveries are permitted
until this timeout has expired.
- </p></div><div class="refsect2" lang="en"><a
name="id1915227"></a><h3>EnableBans</h3><p>Default: 1</p><p>
- When set to 0, this disables BANNING completely in the cluster and thus
nodes can not get banned, even it they break. Don't set to 0.
- </p></div><div class="refsect2" lang="en"><a
name="id1915240"></a><h3>DeterministicIPs</h3><p>Default: 1</p><p>
- When enabled, this tunable makes ctdb try to keep public IP addresses
locked to specific nodes as far as possible. This makes it easier for debugging
since you can know that as long as all nodes are healthy public IP X will
always be hosted by node Y.
- </p><p>
- The cost of using deterministic IP address assignment is that it disables
part of the logic where ctdb tries to reduce the number of public IP assignment
changes in the cluster. This tunable may increase the number of IP
failover/failbacks that are performed on the cluster by a small margin.
- </p></div><div class="refsect2" lang="en"><a
name="id1915260"></a><h3>DisableWhenUnhealthy</h3><p>Default: 0</p><p>
- When set, As soon as a node becomes unhealthy, that node will also
automatically become permanently DISABLED. Once a node is DISABLED, the only
way to make it participate in the cluster again and host services is by
manually enabling the node again using 'ctdb enable'.
- </p><p>
- This disables parts of the resilience and robustness of the cluster and
should ONLY be used when the system administrator is actively monitoring the
cluster, so that nodes can be enabled again.
- </p></div><div class="refsect2" lang="en"><a
name="id1915279"></a><h3>NoIPFailback</h3><p>Default: 0</p><p>
- When set to 1, ctdb will not perform failback of IP addresses when a node
becomes healthy. Ctdb WILL perform failover of public IP addresses when a node
becomes UNHEALTHY, but when the node becomes HEALTHY again, ctdb will not fail
the addresses back.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841694"></a><h3>DatabaseMaxDead</h3><p>Default: 5</p><p>
+ How many dead records per hashchain in the TDB database do we allow before
+ the freelist needs to be processed.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841707"></a><h3>RerecoveryTimeout</h3><p>Default: 10</p><p>
+ Once a recovery has completed, no additional recoveries are permitted
+ until this timeout has expired.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841720"></a><h3>EnableBans</h3><p>Default: 1</p><p>
+ When set to 0, this disables BANNING completely in the cluster and thus
+ nodes can not get banned, even it they break. Don't set to 0 unless you
+ know what you are doing.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841734"></a><h3>DeterministicIPs</h3><p>Default: 0</p><p>
+ When enabled, this tunable makes ctdb try to keep public IP addresses
+ locked to specific nodes as far as possible. This makes it easier for
+ debugging since you can know that as long as all nodes are healthy
+ public IP X will always be hosted by node Y.
+ </p><p>
+ The cost of using deterministic IP address assignment is that it
+ disables part of the logic where ctdb tries to reduce the number of
+ public IP assignment changes in the cluster. This tunable may increase
+ the number of IP failover/failbacks that are performed on the cluster
+ by a small margin.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841754"></a><h3>LCP2PublicIPs</h3><p>Default: 1</p><p>
+ When enabled this switches ctdb to use the LCP2 ip allocation
+ algorithm.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841766"></a><h3>ReclockPingPeriod</h3><p>Default: x</p><p>
+ Obsolete
+ </p></div><div class="refsect2" lang="en"><a
name="id2841778"></a><h3>NoIPFailback</h3><p>Default: 0</p><p>
+ When set to 1, ctdb will not perform failback of IP addresses when a node
+ becomes healthy. Ctdb WILL perform failover of public IP addresses when a
+ node becomes UNHEALTHY, but when the node becomes HEALTHY again, ctdb
+ will not fail the addresses back.
</p><p>
Use with caution! Normally when a node becomes available to the cluster
-ctdb will try to reassign public IP addresses onto the new node as a way to
distribute the workload evenly across the clusternode. Ctdb tries to make sure
that all running nodes have approximately the same number of public addresses
it hosts.
- </p><p>
- When you enable this tunable, CTDB will no longer attempt to rebalance the
cluster by failing IP addresses back to the new nodes. An unbalanced cluster
will therefore remain unbalanced until there is manual intervention from the
administrator. When this parameter is set, you can manually fail public IP
addresses over to the new node(s) using the 'ctdb moveip' command.
- </p></div><div class="refsect2" lang="en"><a
name="id1915306"></a><h3>RecoverPDBBySeqNum</h3><p>Default: 0</p><p>
- When set to non-zero, this will change how the recovery process for
persistent
- databases ar performed.
- By default, when performing a database recovery, for normal as for
persistent
- databases, recovery is record-by-record and recovery process simply
collects
- the most recent version of every individual record.
- </p><p>
- When set to non-zero, persistent databases will instead be recovered
- as a whole db and not by individual records. The node that contains the
highest
- value stored in the record "__db_sequence_number__" is selected and the
copy of
- that nodes database is used as the recovered database.
- </p></div></div><div class="refsect1" lang="en"><a
name="id1915327"></a><h2>LVS</h2><p>
+ ctdb will try to reassign public IP addresses onto the new node as a way
+ to distribute the workload evenly across the clusternode. Ctdb tries to
+ make sure that all running nodes have approximately the same number of
+ public addresses it hosts.
+ </p><p>
+ When you enable this tunable, CTDB will no longer attempt to rebalance
+ the cluster by failing IP addresses back to the new nodes. An unbalanced
+ cluster will therefore remain unbalanced until there is manual
+ intervention from the administrator. When this parameter is set, you can
+ manually fail public IP addresses over to the new node(s) using the
+ 'ctdb moveip' command.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841805"></a><h3>DisableIPFailover</h3><p>Default: 0</p><p>
+ When enabled, ctdb weill not perform failover or failback. Even if a
+ node fails while holding public IPs, ctdb will not recover the IPs or
+ assign them to another node.
+ </p><p>
+ When you enable this tunable, CTDB will no longer attempt to recover
+ the cluster by failing IP addresses over to other nodes. This leads to
+ a service outage until the administrator has manually performed failover
+ to replacement nodes using the 'ctdb moveip' command.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841824"></a><h3>VerboseMemoryNames</h3><p>Default: 0</p><p>
+ This feature consumes additional memory. when used the talloc library
+ will create more verbose names for all talloc allocated objects.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841837"></a><h3>RecdPingTimeout</h3><p>Default: 60</p><p>
+ If the main dameon has not heard a "ping" from the recovery dameon for
+ this many seconds, the main dameon will log a message that the recovery
+ daemon is potentially hung.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841851"></a><h3>RecdFailCount</h3><p>Default: 10</p><p>
+ If the recovery daemon has failed to ping the main dameon for this many
+ consecutive intervals, the main daemon will consider the recovery daemon
+ as hung and will try to restart it to recover.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841864"></a><h3>LogLatencyMs</h3><p>Default: 0</p><p>
+ When set to non-zero, this will make the main daemon log any operation that
+ took longer than this value, in 'ms', to complete.
+ These include "how long time a lockwait child process needed",
+ "how long time to write to a persistent database" but also
+ "how long did it take to get a response to a CALL from a remote node".
+ </p></div><div class="refsect2" lang="en"><a
name="id2841879"></a><h3>RecLockLatencyMs</h3><p>Default: 1000</p><p>
+ When using a reclock file for split brain prevention, if set to non-zero
+ this tunable will make the recovery dameon log a message if the fcntl()
+ call to lock/testlock the recovery file takes longer than this number of
+ ms.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841893"></a><h3>RecoveryDropAllIPs</h3><p>Default: 120</p><p>
+ If we have been stuck in recovery, or stopped, or banned, mode for
+ this many seconds we will force drop all held public addresses.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841906"></a><h3>verifyRecoveryLock</h3><p>Default: 1</p><p>
+ Should we take a fcntl() lock on the reclock file to verify that we are the
+ sole recovery master node on the cluster or not.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841919"></a><h3>DeferredAttachTO</h3><p>Default: 120</p><p>
+ When databases are frozen we do not allow clients to attach to the
+ databases. Instead of returning an error immediately to the application
+ the attach request from the client is deferred until the database
+ becomes available again at which stage we respond to the client.
+ </p><p>
+ This timeout controls how long we will defer the request from the client
+ before timing it out and returning an error to the client.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841938"></a><h3>StatHistoryInterval</h3><p>Default: 1</p><p>
+ Granularity of the statistics collected in the statistics history.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841950"></a><h3>AllowClientDBAttach</h3><p>Default: 1</p><p>
+ When set to 0, clients are not allowed to attach to any databases.
+ This can be used to temporarily block any new processes from attaching
+ to and accessing the databases.
+ </p></div><div class="refsect2" lang="en"><a
name="id2841964"></a><h3>RecoverPDBBySeqNum</h3><p>Default: 0</p><p>
--
CTDB repository
