summaryrefslogtreecommitdiff
path: root/ctdb
diff options
context:
space:
mode:
authorMartin Schwenke <martin@meltin.net>2016-12-10 14:50:21 +1100
committerAmitay Isaacs <amitay@samba.org>2016-12-19 04:07:08 +0100
commitc4eab456ab9f634cd7fa0ce36749432d36d03a2b (patch)
tree59aab3499530935ad7a5a039b8a4ce93948ef473 /ctdb
parent3fc38472c6cf03546ad0a757a457279bd9f46282 (diff)
downloadsamba-c4eab456ab9f634cd7fa0ce36749432d36d03a2b.tar.gz
ctdb-docs: Document that tunables should be set the same on all nodes
Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>
Diffstat (limited to 'ctdb')
-rw-r--r--ctdb/doc/ctdb-tunables.7.xml28
1 files changed, 18 insertions, 10 deletions
diff --git a/ctdb/doc/ctdb-tunables.7.xml b/ctdb/doc/ctdb-tunables.7.xml
index 8143a45a795..1e263dac9a4 100644
--- a/ctdb/doc/ctdb-tunables.7.xml
+++ b/ctdb/doc/ctdb-tunables.7.xml
@@ -30,6 +30,14 @@
</para>
<para>
+ Unless otherwise stated, tunables should be set to the same
+ value on all nodes. Setting tunables to different values across
+ nodes may produce unexpected results. Future releases may set
+ (some or most) tunables globally across the cluster but doing so
+ is currently a manual process.
+ </para>
+
+ <para>
The tunable variables are listed alphabetically.
</para>
@@ -177,13 +185,12 @@
<title>EnableBans</title>
<para>Default: 1</para>
<para>
- This parameter allows ctdb to ban a node if the node is misbehaving.
+ This parameter allows ctdb to ban a node if the node is misbehaving.
</para>
<para>
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. You should set
- this to the same value on all nodes to avoid unexpected behaviour.
+ set to 0 unless you know what you are doing.
</para>
</refsect2>
@@ -362,10 +369,9 @@
If no nodes are HEALTHY then by default ctdb will happily host
public IPs on disabled (unhealthy or administratively disabled)
nodes. This can cause problems, for example if the underlying
- cluster filesystem is not mounted. When set to 1 on a node and
- that node is disabled, any IPs hosted by this node will be
- released and the node will not takeover any IPs until it is no
- longer disabled.
+ cluster filesystem is not mounted. When set to 1 and a node
+ is disabled, any IPs hosted by this node will be released and
+ the node will not takeover any IPs until it is no longer disabled.
</para>
</refsect2>
@@ -374,9 +380,11 @@
<para>Default: 0</para>
<para>
When set to 1, ctdb will not allow IP addresses to be failed
- over onto this node. Any IP addresses that the node currently
- hosts will remain on the node but no new IP addresses can be
- failed over to the node.
+ over to other nodes. Any IP addresses already hosted on
+ healthy nodes will remain. Usually IP addresses hosted on
+ unhealthy nodes will also remain, if NoIPHostOnAllDisabled is
+ 0. However, if NoIPHostOnAllDisabled is 1 then IP addresses
+ will be released by unhealthy nodes and will become un-hosted.
</para>
</refsect2>