[SCM] Samba Shared Repository - branch master updated
Amitay Isaacs
amitay at samba.org
Thu Mar 10 05:52:03 UTC 2016
The branch, master has been updated
via fa8bd41 ctdb-tunables: Mark tunable DeferredRebalanceOnNodeAdd obsolete
via c9e69a4 ctdb-recoverd: Drop use of DeferredRebalanceOnNodeAdd tunable
via d678684 ctdb-tools: Drop "ctdb rebalancenode"
via aaa57fb ctdb-tools: Drop "ctdb rebalanceip"
via 21ec67e ctdb-doc: Drop outdated NEWS file
via 963d082 ctdb-doc: Update ctdb man page
via 2db5e3e ctdb-doc: Update ctdb man page
via bd23b43 ctdb-tunables: Fix the implementation of LIST_TUNABLES control
via 700f393 ctdb-recovery-helper: Get tunables first, so control timeout can be set
via 3680aba ctdb-doc: Add documentation for missing tunables
via e253908 ctdb-doc: Update tunables documentation
via 4a78200 ctdb-tunables: Mark tunable ReclockPingPeriod obsolete
via 73ab0f9 ctdb-tunables: Mark tunable MaxRedirectCount obsolete
via aa700de ctdb-tunables: Add missing flags in the initializer
via 4bf6cab ctdb-doc: Sort the tunable variables in alphabetical order
via 05051bd ctdb-tests: Add a new NFS tickle test for the releasing node
via 6b51ea3 ctdb-tests: Allow tcptickle_sniff_wait_show() to filter by MAC address
via 0328098 ctdb-tests: Re-indent and re-format some functions
via df2d752 ctdb-tests: Fix CIFS tickle test
via 12879b3 ctdb-tests: Fix description of NFS tickle test
from cb51e8d s4/heimdal/lib/krb5/pac.c: typo
https://git.samba.org/?p=samba.git;a=shortlog;h=master
- Log -----------------------------------------------------------------
commit fa8bd41009599ac4adb746cf43ea41530bb27812
Author: Martin Schwenke <martin at meltin.net>
Date: Wed Mar 9 12:06:21 2016 +1100
ctdb-tunables: Mark tunable DeferredRebalanceOnNodeAdd obsolete
Signed-off-by: Martin Schwenke <martin at meltin.net>
Reviewed-by: Amitay Isaacs <amitay at gmail.com>
Autobuild-User(master): Amitay Isaacs <amitay at samba.org>
Autobuild-Date(master): Thu Mar 10 06:51:46 CET 2016 on sn-devel-144
commit c9e69a4b2e91ae2b1d6f8b5b0bfe64b0bd6dc710
Author: Martin Schwenke <martin at meltin.net>
Date: Tue Mar 8 16:36:04 2016 +1100
ctdb-recoverd: Drop use of DeferredRebalanceOnNodeAdd tunable
If set, this was used to setup an IP takeover run on a timer after
certain updates to the public IP address configuration (e.g. "ctdb
addip").
However, "ctdb reloadips" completely manages public IP reconfiguration
and avoids the anomalies that DeferredRebalanceOnNodeAdd was
introduced to work around.
Signed-off-by: Martin Schwenke <martin at meltin.net>
Reviewed-by: Amitay Isaacs <amitay at gmail.com>
commit d67868469521341aa92c589a0bb6df90b150d555
Author: Martin Schwenke <martin at meltin.net>
Date: Tue Mar 8 16:29:56 2016 +1100
ctdb-tools: Drop "ctdb rebalancenode"
This was a workaround for trying to ensure public IP addresses are
properly rebalanced after running "ctdb addip" on multiple nodes.
"ctdb reloadips" is a better solution.
Signed-off-by: Martin Schwenke <martin at meltin.net>
Reviewed-by: Amitay Isaacs <amitay at gmail.com>
commit aaa57fbcb392061f8fbb5a12fd0e6a7be934ab66
Author: Martin Schwenke <martin at meltin.net>
Date: Tue Mar 8 16:20:03 2016 +1100
ctdb-tools: Drop "ctdb rebalanceip"
This is undocumented and is not needed. It was a workaround for
trying to ensure public IP addresses are properly rebalanced after
running "ctdb addip" on multiple nodes. "ctdb reloadips" is a better
solution.
Signed-off-by: Martin Schwenke <martin at meltin.net>
Reviewed-by: Amitay Isaacs <amitay at gmail.com>
commit 21ec67e2e9233b4ef1fe257ed240d7a699a7d155
Author: Martin Schwenke <martin at meltin.net>
Date: Tue Mar 8 16:30:41 2016 +1100
ctdb-doc: Drop outdated NEWS file
Signed-off-by: Martin Schwenke <martin at meltin.net>
Reviewed-by: Amitay Isaacs <amitay at gmail.com>
commit 963d0825fc1507d202b4f85f30189f4db59f480d
Author: Amitay Isaacs <amitay at gmail.com>
Date: Tue Mar 8 15:23:12 2016 +1100
ctdb-doc: Update ctdb man page
Update ctdb statistics and ctdb dbstatistics output.
Signed-off-by: Amitay Isaacs <amitay at gmail.com>
Reviewed-by: Martin Schwenke <martin at meltin.net>
commit 2db5e3ed71794efc39676a510a45f7290ba97f53
Author: Amitay Isaacs <amitay at gmail.com>
Date: Tue Mar 8 15:17:24 2016 +1100
ctdb-doc: Update ctdb man page
Do not use obsolete tunables in examples.
Signed-off-by: Amitay Isaacs <amitay at gmail.com>
Reviewed-by: Martin Schwenke <martin at meltin.net>
commit bd23b43bfe9abe586a222673bede4414b6299518
Author: Amitay Isaacs <amitay at gmail.com>
Date: Tue Mar 8 15:12:42 2016 +1100
ctdb-tunables: Fix the implementation of LIST_TUNABLES control
Do not assume the first tunable is not obsolete.
Signed-off-by: Amitay Isaacs <amitay at gmail.com>
Reviewed-by: Martin Schwenke <martin at meltin.net>
commit 700f39372ad9c893f8eb8884cd24999dc7026e60
Author: Amitay Isaacs <amitay at gmail.com>
Date: Tue Mar 8 14:51:59 2016 +1100
ctdb-recovery-helper: Get tunables first, so control timeout can be set
During the recovery process, the timeout value for sending all controls
is decided by RecoverTimeout tunable. So in the recovery process,
first get the tunables, so the control timeout gets set correctly.
Signed-off-by: Amitay Isaacs <amitay at gmail.com>
Reviewed-by: Martin Schwenke <martin at meltin.net>
commit 3680aba2126d967a5518ab2d35d9e6d3f338e75e
Author: Amitay Isaacs <amitay at gmail.com>
Date: Tue Mar 8 14:37:41 2016 +1100
ctdb-doc: Add documentation for missing tunables
Signed-off-by: Amitay Isaacs <amitay at gmail.com>
Reviewed-by: Martin Schwenke <martin at meltin.net>
commit e2539088e023ad88d314467a6a42b52c0decba77
Author: Amitay Isaacs <amitay at gmail.com>
Date: Mon Mar 7 19:26:43 2016 +1100
ctdb-doc: Update tunables documentation
Signed-off-by: Amitay Isaacs <amitay at gmail.com>
Reviewed-by: Martin Schwenke <martin at meltin.net>
commit 4a78200f4359084aefb6abfbd78a6c8f6d46a199
Author: Amitay Isaacs <amitay at gmail.com>
Date: Mon Mar 7 18:19:02 2016 +1100
ctdb-tunables: Mark tunable ReclockPingPeriod obsolete
Signed-off-by: Amitay Isaacs <amitay at gmail.com>
Reviewed-by: Martin Schwenke <martin at meltin.net>
commit 73ab0f991154c2651ebe737c9d9d093eaf65c652
Author: Amitay Isaacs <amitay at gmail.com>
Date: Mon Mar 7 18:02:02 2016 +1100
ctdb-tunables: Mark tunable MaxRedirectCount obsolete
Signed-off-by: Amitay Isaacs <amitay at gmail.com>
Reviewed-by: Martin Schwenke <martin at meltin.net>
commit aa700deb64127726bfe1cd0fab519662c000ec11
Author: Amitay Isaacs <amitay at gmail.com>
Date: Mon Mar 7 17:10:43 2016 +1100
ctdb-tunables: Add missing flags in the initializer
Signed-off-by: Amitay Isaacs <amitay at gmail.com>
Reviewed-by: Martin Schwenke <martin at meltin.net>
commit 4bf6cab4a1e1c11f79fde40fc8b9ae29b0f00e35
Author: Amitay Isaacs <amitay at gmail.com>
Date: Mon Mar 7 17:05:11 2016 +1100
ctdb-doc: Sort the tunable variables in alphabetical order
Signed-off-by: Amitay Isaacs <amitay at gmail.com>
Reviewed-by: Martin Schwenke <martin at meltin.net>
commit 05051bd115726657615412a3bbdeb6f0ad7f0396
Author: Martin Schwenke <martin at meltin.net>
Date: Tue Mar 8 13:37:42 2016 +1100
ctdb-tests: Add a new NFS tickle test for the releasing node
Current NFS and CIFS tickle tests do not test the killtcp
functionality on the releasing node. 2-way killing is done for NFS,
so this test explicitly looks for packets from the releasing node.
Signed-off-by: Martin Schwenke <martin at meltin.net>
Reviewed-by: Amitay Isaacs <amitay at gmail.com>
commit 6b51ea35fdc25aa5109e8c9f4596e346832acd95
Author: Martin Schwenke <martin at meltin.net>
Date: Tue Mar 8 10:03:12 2016 +1100
ctdb-tests: Allow tcptickle_sniff_wait_show() to filter by MAC address
tcpdump does not support filtering on MAC address when reading from a
file. Therefore, this is implemented by conditionally using grep to
filter the output of tcpdump.
Signed-off-by: Martin Schwenke <martin at meltin.net>
Reviewed-by: Amitay Isaacs <amitay at gmail.com>
commit 032809828567c677b80d9760f67c345a8d250037
Author: Martin Schwenke <martin at meltin.net>
Date: Tue Mar 8 13:32:35 2016 +1100
ctdb-tests: Re-indent and re-format some functions
This makes the next commit much easier to read.
Signed-off-by: Martin Schwenke <martin at meltin.net>
Reviewed-by: Amitay Isaacs <amitay at gmail.com>
commit df2d752e29e95ce3773182416d5e6d91ac1c6066
Author: Martin Schwenke <martin at meltin.net>
Date: Tue Mar 8 09:59:33 2016 +1100
ctdb-tests: Fix CIFS tickle test
There's a tiny chance that the connection information may not be
transferred to other nodes quickly enough, so add an explicit wait.
Also clean up the description and recognise that it is the takeover
node that does the tickling.
Signed-off-by: Martin Schwenke <martin at meltin.net>
Reviewed-by: Amitay Isaacs <amitay at gmail.com>
commit 12879b353f329286d7771be89609419c1d3e4356
Author: Martin Schwenke <martin at meltin.net>
Date: Tue Mar 8 09:44:44 2016 +1100
ctdb-tests: Fix description of NFS tickle test
Signed-off-by: Martin Schwenke <martin at meltin.net>
Reviewed-by: Amitay Isaacs <amitay at gmail.com>
-----------------------------------------------------------------------
Summary of changes:
ctdb/NEWS | 354 ---------------
ctdb/doc/ctdb-tunables.7.xml | 681 +++++++++++++++-------------
ctdb/doc/ctdb.1.xml | 137 +++---
ctdb/packaging/RPM/ctdb.spec.in | 2 +-
ctdb/server/ctdb_recoverd.c | 32 --
ctdb/server/ctdb_recovery_helper.c | 97 ++--
ctdb/server/ctdb_takeover.c | 2 +-
ctdb/server/ctdb_tunables.c | 32 +-
ctdb/tests/complex/30_nfs_tickle_killtcp.sh | 69 +++
ctdb/tests/complex/31_nfs_tickle.sh | 19 +-
ctdb/tests/complex/32_cifs_tickle.sh | 30 +-
ctdb/tests/complex/scripts/local.bash | 64 ++-
ctdb/tools/ctdb.c | 113 -----
13 files changed, 635 insertions(+), 997 deletions(-)
delete mode 100644 ctdb/NEWS
create mode 100755 ctdb/tests/complex/30_nfs_tickle_killtcp.sh
Changeset truncated at 500 lines:
diff --git a/ctdb/NEWS b/ctdb/NEWS
deleted file mode 100644
index 6dee537..0000000
--- a/ctdb/NEWS
+++ /dev/null
@@ -1,354 +0,0 @@
-Changes in CTDB 2.5.1
-=====================
-
-Important bug fixes
--------------------
-
-* The locking code now correctly implements a per-database active
- locks limit. Whole database lock requests can no longer be denied
- because there are too many active locks - this is particularly
- important for freezing databases during recovery.
-
-* The debug_locks.sh script locks against itself. If it is already
- running then subsequent invocations will exit immediately.
-
-* ctdb tool commands that operate on databases now work correctly when
- a database ID is given.
-
-* Various code fixes for issues found by Coverity.
-
-Important internal changes
---------------------------
-
-* statd-callout has been updated so that statd client information is
- always up-to-date across the cluster. This is implemented by
- storing the client information in a persistent database using a new
- "ctdb ptrans" command.
-
-* The transaction code for persistent databases now retries until it
- is able to take the transaction lock. This makes the transation
- semantics compatible with Samba's implementation.
-
-* Locking helpers are created with vfork(2) instead of fork(2),
- providing a performance improvement.
-
-* config.guess has been updated to the latest upstream version so CTDB
- should build on more platforms.
-
-
-Changes in CTDB 2.5
-===================
-
-User-visible changes
---------------------
-
-* The default location of the ctdbd socket is now:
-
- /var/run/ctdb/ctdbd.socket
-
- If you currently set CTDB_SOCKET in configuration then unsetting it
- will probably do what you want.
-
-* The default location of CTDB TDB databases is now:
-
- /var/lib/ctdb
-
- If you only set CTDB_DBDIR (to the old default of /var/ctdb) then
- you probably want to move your databases to /var/lib/ctdb, drop your
- setting of CTDB_DBDIR and just use the default.
-
- To maintain the database files in /var/ctdb you will need to set
- CTDB_DBDIR, CTDB_DBDIR_PERSISTENT and CTDB_DBDIR_STATE, since all of
- these have moved.
-
-* Use of CTDB_OPTIONS to set ctdbd command-line options is no longer
- supported. Please use individual configuration variables instead.
-
-* Obsolete tunables VacuumDefaultInterval, VacuumMinInterval and
- VacuumMaxInterval have been removed. Setting them had no effect but
- if you now try to set them in a configuration files via CTDB_SET_X=Y
- then CTDB will not start.
-
-* Much improved manual pages. Added new manpages ctdb(7),
- ctdbd.conf(5), ctdb-tunables(7). Still some work to do.
-
-* Most CTDB-specific configuration can now be set in
- /etc/ctdb/ctdbd.conf.
-
- This avoids cluttering distribution-specific configuration files,
- such as /etc/sysconfig/ctdb. It also means that we can say: see
- ctdbd.conf(5) for more details. :-)
-
-* Configuration variable NFS_SERVER_MODE is deprecated and has been
- replaced by CTDB_NFS_SERVER_MODE. See ctdbd.conf(5) for more
- details.
-
-* "ctdb reloadips" is much improved and should be used for reloading
- the public IP configuration.
-
- This commands attempts to yield much more predictable IP allocations
- than using sequences of delip and addip commands. See ctdb(1) for
- details.
-
-* Ability to pass comma-separated string to ctdb(1) tool commands via
- the -n option is now documented and works for most commands. See
- ctdb(1) for details.
-
-* "ctdb rebalancenode" is now a debugging command and should not be
- used in normal operation. See ctdb(1) for details.
-
-* "ctdb ban 0" is now invalid.
-
- This was documented as causing a permanent ban. However, this was
- not implemented and caused an "unban" instead. To avoid confusion,
- 0 is now an invalid ban duration. To administratively "ban" a node
- use "ctdb stop" instead.
-
-* The systemd configuration now puts the PID file in /run/ctdb (rather
- than /run/ctdbd) for consistency with the initscript and other uses
- of /var/run/ctdb.
-
-Important bug fixes
--------------------
-
-* Traverse regression fixed.
-
-* The default recovery method for persistent databases has been
- changed to use database sequence numbers instead of doing
- record-by-record recovery (using record sequence numbers). This
- fixes issues including registry corruption.
-
-* Banned nodes are no longer told to run the "ipreallocated" event
- during a takeover run, when in fallback mode with nodes that don't
- support the IPREALLOCATED control.
-
-Important internal changes
---------------------------
-
-* Persistent transactions are now compatible with Samba and work
- reliably.
-
-* The recovery master role has been made more stable by resetting the
- priority time each time a node becomes inactive. This means that
- nodes that are active for a long time are more likely to retain the
- recovery master role.
-
-* The incomplete libctdb library has been removed.
-
-* Test suite now starts ctdbd with the --sloppy-start option to speed
- up startup. However, this should not be done in production.
-
-
-Changes in CTDB 2.4
-===================
-
-User-visible changes
---------------------
-
-* A missing network interface now causes monitoring to fail and the
- node to become unhealthy.
-
-* Changed ctdb command's default control timeout from 3s to 10s.
-
-* debug-hung-script.sh now includes the output of "ctdb scriptstatus"
- to provide more information.
-
-Important bug fixes
--------------------
-
-* Starting CTDB daemon by running ctdbd directly should not remove
- existing unix socket unconditionally.
-
-* ctdbd once again successfully kills client processes on releasing
- public IPs. It was checking for them as tracked child processes
- and not finding them, so wasn't killing them.
-
-* ctdbd_wrapper now exports CTDB_SOCKET so that child processes of
- ctdbd (such as uses of ctdb in eventscripts) use the correct socket.
-
-* Always use Jenkins hash when creating volatile databases. There
- were a few places where TDBs would be attached with the wrong flags.
-
-* Vacuuming code fixes in CTDB 2.2 introduced bugs in the new code
- which led to header corruption for empty records. This resulted
- in inconsistent headers on two nodes and a request for such a record
- keeps bouncing between nodes indefinitely and logs "High hopcount"
- messages in the log. This also caused performance degradation.
-
-* ctdbd was losing log messages at shutdown because they weren't being
- given time to flush. ctdbd now sleeps for a second during shutdown
- to allow time to flush log messages.
-
-* Improved socket handling introduced in CTDB 2.2 caused ctdbd to
- process a large number of packets available on single FD before
- polling other FDs. Use fixed size queue buffers to allow fair
- scheduling across multiple FDs.
-
-Important internal changes
---------------------------
-
-* A node that fails to take/release multiple IPs will only incur a
- single banning credit. This makes a brief failure less likely to
- cause node to be banned.
-
-* ctdb killtcp has been changed to read connections from stdin and
- 10.interface now uses this feature to improve the time taken to kill
- connections.
-
-* Improvements to hot records statistics in ctdb dbstatistics.
-
-* Recovery daemon now assembles up-to-date node flags information
- from remote nodes before checking if any flags are inconsistent and
- forcing a recovery.
-
-* ctdbd no longer creates multiple lock sub-processes for the same
- key. This reduces the number of lock sub-processes substantially.
-
-* Changed the nfsd RPC check failure policy to failover quickly
- instead of trying to repair a node first by restarting NFS. Such
- restarts would often hang if the cause of the RPC check failure was
- the cluster filesystem or storage.
-
-* Logging improvements relating to high hopcounts and sticky records.
-
-* Make sure lower level tdb messages are logged correctly.
-
-* CTDB commands disable/enable/stop/continue are now resilient to
- individual control failures and retry in case of failures.
-
-
-Changes in CTDB 2.3
-===================
-
-User-visible changes
---------------------
-
-* 2 new configuration variables for 60.nfs eventscript:
-
- - CTDB_MONITOR_NFS_THREAD_COUNT
- - CTDB_NFS_DUMP_STUCK_THREADS
-
- See ctdb.sysconfig for details.
-
-* Removed DeadlockTimeout tunable. To enable debug of locking issues set
-
- CTDB_DEBUG_LOCKS=/etc/ctdb/debug_locks.sh
-
-* In overall statistics and database statistics, lock buckets have been
- updated to use following timings:
-
- < 1ms, < 10ms, < 100ms, < 1s, < 2s, < 4s, < 8s, < 16s, < 32s, < 64s, >= 64s
-
-* Initscript is now simplified with most CTDB-specific functionality
- split out to ctdbd_wrapper, which is used to start and stop ctdbd.
-
-* Add systemd support.
-
-* CTDB subprocesses are now given informative names to allow them to
- be easily distinguished when using programs like "top" or "perf".
-
-Important bug fixes
--------------------
-
-* ctdb tool should not exit from a retry loop if a control times out
- (e.g. under high load). This simple fix will stop an exit from the
- retry loop on any error.
-
-* When updating flags on all nodes, use the correct updated flags. This
- should avoid wrong flag change messages in the logs.
-
-* The recovery daemon will not ban other nodes if the current node
- is banned.
-
-* ctdb dbstatistics command now correctly outputs database statistics.
-
-* Fixed a panic with overlapping shutdowns (regression in 2.2).
-
-* Fixed 60.ganesha "monitor" event (regression in 2.2).
-
-* Fixed a buffer overflow in the "reloadips" implementation.
-
-* Fixed segmentation faults in ping_pong (called with incorrect
- argument) and test binaries (called when ctdbd not running).
-
-Important internal changes
---------------------------
-
-* The recovery daemon on stopped or banned node will stop participating in any
- cluster activity.
-
-* Improve cluster wide database traverse by sending the records directly from
- traverse child process to requesting node.
-
-* TDB checking and dropping of all IPs moved from initscript to "init"
- event in 00.ctdb.
-
-* To avoid "rogue IPs" the release IP callback now fails if the
- released IP is still present on an interface.
-
-
-Changes in CTDB 2.2
-===================
-
-User-visible changes
---------------------
-
-* The "stopped" event has been removed.
-
- The "ipreallocated" event is now run when a node is stopped. Use
- this instead of "stopped".
-
-* New --pidfile option for ctdbd, used by initscript
-
-* The 60.nfs eventscript now uses configuration files in
- /etc/ctdb/nfs-rpc-checks.d/ for timeouts and actions instead of
- hardcoding them into the script.
-
-* Notification handler scripts can now be dropped into /etc/ctdb/notify.d/.
-
-* The NoIPTakeoverOnDisabled tunable has been renamed to
- NoIPHostOnAllDisabled and now works properly when set on individual
- nodes.
-
-* New ctdb subcommand "runstate" prints the current internal runstate.
- Runstates are used for serialising startup.
-
-Important bug fixes
--------------------
-
-* The Unix domain socket is now set to non-blocking after the
- connection succeeds. This avoids connections failing with EAGAIN
- and not being retried.
-
-* Fetching from the log ringbuffer now succeeds if the buffer is full.
-
-* Fix a severe recovery bug that can lead to data corruption for SMB clients.
-
-* The statd-callout script now runs as root via sudo.
-
-* "ctdb delip" no longer fails if it is unable to move the IP.
-
-* A race in the ctdb tool's ipreallocate code was fixed. This fixes
- potential bugs in the "disable", "enable", "stop", "continue",
- "ban", "unban", "ipreallocate" and "sync" commands.
-
-* The monitor cancellation code could sometimes hang indefinitely.
- This could cause "ctdb stop" and "ctdb shutdown" to fail.
-
-Important internal changes
---------------------------
-
-* The socket I/O handling has been optimised to improve performance.
-
-* IPs will not be assigned to nodes during CTDB initialisation. They
- will only be assigned to nodes that are in the "running" runstate.
-
-* Improved database locking code. One improvement is to use a
- standalone locking helper executable - the avoids creating many
- forked copies of ctdbd and potentially running a node out of memory.
-
-* New control CTDB_CONTROL_IPREALLOCATED is now used to generate
- "ipreallocated" events.
-
-* Message handlers are now indexed, providing a significant
- performance improvement.
diff --git a/ctdb/doc/ctdb-tunables.7.xml b/ctdb/doc/ctdb-tunables.7.xml
index 6c164f3..591dcf5 100644
--- a/ctdb/doc/ctdb-tunables.7.xml
+++ b/ctdb/doc/ctdb-tunables.7.xml
@@ -29,39 +29,28 @@
<command>getvar</command> commands for more details.
</para>
- <refsect2>
- <title>MaxRedirectCount</title>
- <para>Default: 3</para>
- <para>
- 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.
+ <para>
+ The tunable variables are listed alphabetically.
+ </para>
- 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.
- </para>
+ <refsect2>
+ <title>AllowClientDBAttach</title>
+ <para>Default: 1</para>
<para>
- 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.
+ 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. This is mainly used
+ for detaching a volatile database using 'ctdb detach'.
</para>
</refsect2>
<refsect2>
- <title>SeqnumInterval</title>
- <para>Default: 1000</para>
- <para>
- 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.
- </para>
+ <title>AllowUnhealthyDBRead</title>
+ <para>Default: 0</para>
<para>
- 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.
+ When set to 1, ctdb allows database traverses to read unhealthy
+ databases. By default, ctdb does not allow reading records from
+ unhealthy databases.
</para>
</refsect2>
@@ -69,98 +58,132 @@
<title>ControlTimeout</title>
<para>Default: 60</para>
<para>
- This is the default
- setting for timeout for when sending a control message to either the
- local or a remote ctdb daemon.
+ This is the default setting for timeout for when sending a
+ control message to either the local or a remote ctdb daemon.
</para>
</refsect2>
<refsect2>
- <title>TraverseTimeout</title>
- <para>Default: 20</para>
+ <title>DatabaseHashSize</title>
+ <para>Default: 100001</para>
<para>
- 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.
+ Number of the hash chains for the local store of the tdbs that
+ ctdb manages.
</para>
</refsect2>
<refsect2>
- <title>KeepaliveInterval</title>
+ <title>DatabaseMaxDead</title>
<para>Default: 5</para>
<para>
- How often in seconds should the nodes send keepalives to eachother.
+ Maximum number of dead records per hash chain for the tdb databses
+ managed by ctdb.
</para>
</refsect2>
<refsect2>
- <title>KeepaliveLimit</title>
- <para>Default: 5</para>
+ <title>DBRecordCountWarn</title>
+ <para>Default: 100000</para>
<para>
- After how many keepalive intervals without any traffic should a node
- wait until marking the peer as DISCONNECTED.
+ When set to non-zero, ctdb will log a warning during recovery if
+ a database has more than this many records. This will produce a
+ warning if a database grows uncontrollably with orphaned records.
</para>
+ </refsect2>
+
+ <refsect2>
+ <title>DBRecordSizeWarn</title>
+ <para>Default: 10000000</para>
<para>
- 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.
+ When set to non-zero, ctdb will log a warning during recovery
+ if a single record is bigger than this size. This will produce
+ a warning if a database record grows uncontrollably.
</para>
</refsect2>
<refsect2>
- <title>RecoverTimeout</title>
- <para>Default: 20</para>
+ <title>DBSizeWarn</title>
+ <para>Default: 1000000000</para>
<para>
- 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.
+ When set to non-zero, ctdb will log a warning during recovery if
+ a database size is bigger than this. This will produce a warning
+ if a database grows uncontrollably.
</para>
</refsect2>
--
Samba Shared Repository
More information about the samba-cvs
mailing list