ctdb-doc: Add documentation for missing tunables

Signed-off-by: Amitay Isaacs <amitay@gmail.com>
Reviewed-by: Martin Schwenke <martin@meltin.net>

diff --git a/ctdb/doc/ctdb-tunables.7.xml b/ctdb/doc/ctdb-tunables.7.xml
index 10b0340bc37bd067fb19e82e3b62e223681c5757..591dcf5181f345c8cab2f9f53aa965d7f05b88e6 100644 (file)
--- a/ctdb/doc/ctdb-tunables.7.xml
+++ b/ctdb/doc/ctdb-tunables.7.xml
@@ -44,6 +44,16 @@
       </para>
     </refsect2>
 
+    <refsect2>
+      <title>AllowUnhealthyDBRead</title>
+      <para>Default: 0</para>
+      <para>
+       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>
+
     <refsect2>
       <title>ControlTimeout</title>
       <para>Default: 60</para>
@@ -267,6 +277,17 @@
       </para>
     </refsect2>
 
+    <refsect2>
+      <title>LockProcessesPerDB</title>
+      <para>Default: 200</para>
+      <para>
+       This is the maximum number of lock helper processes ctdb will
+       create for obtaining record locks.  When ctdb cannot get a record
+       lock without blocking, it creates a helper process that waits
+       for the lock to be obtained.
+      </para>
+    </refsect2>
+
     <refsect2>
       <title>LogLatencyMs</title>
       <para>Default: 0</para>
@@ -279,6 +300,16 @@
       </para>
     </refsect2>
 
+    <refsect2>
+      <title>MaxQueueDropMsg</title>
+      <para>Default: 1000000</para>
+      <para>
+       This is the maximum number of messages to be queued up for
+       a client before ctdb will treat the client as hung and will
+       terminate the client connection.
+      </para>
+    </refsect2>
+
     <refsect2>
       <title>MonitorInterval</title>
       <para>Default: 15</para>
@@ -349,6 +380,19 @@
       </para>
     </refsect2>
 
+    <refsect2>
+      <title>PullDBPreallocation</title>
+      <para>Default: 10*1024*1024</para>
+      <para>
+       This is the size of a record buffer to pre-allocate for sending
+       reply to PULLDB control. Usually record buffer starts with size
+       of the first record and gets reallocated every time a new record
+       is added to the record buffer. For a large number of records,
+       this can be very inefficient to grow the record buffer one record
+       at a time.
+      </para>
+    </refsect2>
+
     <refsect2>
       <title>RecdFailCount</title>
       <para>Default: 10</para>
@@ -551,6 +595,17 @@
       </para>
     </refsect2>
 
+    <refsect2>
+      <title>TDBMutexEnabled</title>
+      <para>Default: 0</para>
+      <para>
+       This paramter enables TDB_MUTEX_LOCKING feature on volatile
+       databases if the robust mutexes are supported. This optimizes the
+       record locking using robust mutexes and is much more efficient
+       that using posix locks.
+      </para>
+    </refsect2>
+
     <refsect2>
       <title>TickleUpdateInterval</title>
       <para>Default: 20</para>