summaryrefslogtreecommitdiff
path: root/ctdb/doc
diff options
context:
space:
mode:
authorAmitay Isaacs <amitay@gmail.com>2013-10-28 18:49:51 +1100
committerAmitay Isaacs <amitay@gmail.com>2013-10-28 18:51:22 +1100
commitfc7f3358437b5b6d27b4e03ee477a9e7406b87e3 (patch)
tree4ca4571d1153daef7eef77f213144acbed993578 /ctdb/doc
parenta5c4794048e47e7db1d831adb77fb88f9e1ff8ac (diff)
downloadsamba-fc7f3358437b5b6d27b4e03ee477a9e7406b87e3.tar.gz
daemon: Change the default recovery method for persistent databases
Use sequence numbers to do recovery for persistent databases instead of RSNs. This fixes the problem of registry corruption during recovery. Signed-off-by: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit 56486d1c01cc8ad0e4b8cee7a22429e72e50f03d)
Diffstat (limited to 'ctdb/doc')
-rw-r--r--ctdb/doc/ctdbd.1.xml11
1 files changed, 7 insertions, 4 deletions
diff --git a/ctdb/doc/ctdbd.1.xml b/ctdb/doc/ctdbd.1.xml
index 111a8f40ca4..75974cf708d 100644
--- a/ctdb/doc/ctdbd.1.xml
+++ b/ctdb/doc/ctdbd.1.xml
@@ -1049,11 +1049,9 @@
</refsect2>
<refsect2><title>RecoverPDBBySeqNum</title>
- <para>Default: 0</para>
+ <para>Default: 1</para>
<para>
- 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
+ When set to zero, database recovery for persistent databases is
record-by-record and recovery process simply collects the most recent
version of every individual record.
</para>
@@ -1063,6 +1061,11 @@
highest value stored in the record "__db_sequence_number__" is selected
and the copy of that nodes database is used as the recovered database.
</para>
+ <para>
+ By default, recovery of persistent databses is done using
+ __db_sequence_number__ record.
+ </para>
+
</refsect2>
<refsect2><title>FetchCollapse</title>