WHATSNEW: Documentation CTDB changes for v4.4

Signed-off-by: Martin Schwenke <martin@meltin.net>
Signed-off-by: Amitay Isaacs <amitay@gmail.com>
Autobuild-User(master): Amitay Isaacs <amitay@samba.org>
Autobuild-Date(master): Mon Jan 25 16:47:54 CET 2016 on sn-devel-144

diff --git a/WHATSNEW.txt b/WHATSNEW.txt
index e070b9feec3b13c73b5f5187b88d72d4964ffa7e..e396ff9fb222a26b6bb2c4d981b67a52142760c0 100644 (file)
--- a/WHATSNEW.txt
+++ b/WHATSNEW.txt
@@ -44,12 +44,60 @@ smb.conf changes
 CTDB changes
 ------------
 
+* CTDB now uses a newly implemented parallel database recovery scheme
+  that avoids deadlocks with smbd.
+
+  In certain circumstances CTDB and smbd could deadlock.  The new
+  recovery implementation avoid this.  It also provides improved
+  recovery performance.
+
+* All files are now installed into and referred to by the paths
+  configured at build time.  Therefore, CTDB will now work properly
+  when installed into the default location at /usr/local.
+
+* Public CTDB header files are no longer installed, since Samba and
+  CTDB are built from within the same source tree.
+
+* CTDB_DBDIR can now be set to tmpfs[:<tmpfs-options>]
+
+  This will cause volatile TDBs to be located in a tmpfs.  This can
+  help to avoid performance problems associated with contention on the
+  disk where volatile TDBs are usually stored.  See ctdbd.conf(5) for
+  more details.
+
 * Configuration variable CTDB_NATGW_SLAVE_ONLY is no longer used.
   Instead, nodes should be annotated with the "slave-only" option in
   the CTDB NAT gateway nodes file.  This file must be consistent
   across nodes in a NAT gateway group.  See ctdbd.conf(5) for more
   details.
 
+* New event script 05.system allows various system resources to be
+  monitored
+
+  This can be helpful for explaining poor performance or unexpected
+  behaviour.  New configuration variables are
+  CTDB_MONITOR_FILESYSTEM_USAGE, CTDB_MONITOR_MEMORY_USAGE and
+  CTDB_MONITOR_SWAP_USAGE.  Default values cause warnings to be
+  logged.  See the SYSTEM RESOURCE MONITORING CONFIGURATION in
+  ctdbd.conf(5) for more information.
+
+  The memory, swap and filesystem usage monitoring previously found in
+  00.ctdb and 40.fs_use is no longer available.  Therefore,
+  configuration variables CTDB_CHECK_FS_USE, CTDB_MONITOR_FREE_MEMORY,
+  CTDB_MONITOR_FREE_MEMORY_WARN and CTDB_CHECK_SWAP_IS_NOT_USED are
+  now ignored.
+
+* The 62.cnfs eventscript has been removed.  To get a similar effect
+  just do something like this:
+
+      mmaddcallback ctdb-disable-on-quorumLoss \
+        --command /usr/bin/ctdb \
+        --event quorumLoss --parms "disable"
+
+      mmaddcallback ctdb-enable-on-quorumReached \
+        --command /usr/bin/ctdb \
+        --event quorumReached --parms "enable"
+
 * The CTDB tunable parameter EventScriptTimeoutCount has been renamed
   to MonitorTimeoutCount
 
@@ -58,6 +106,13 @@ CTDB changes
   Configurations containing CTDB_SET_EventScriptTimeoutCount=<n> will
   cause CTDB to fail at startup.  Useful messages will be logged.
 
+* The commandline option "-n all" to CTDB tool has been removed.
+
+  The option was not uniformly implemented for all the commands.
+  Instead of command "ctdb ip -n all", use "ctdb ip all".
+
+* All CTDB current manual pages are now correctly installed
+
 KNOWN ISSUES
 ============