7 * 2 new configuration variables for 60.nfs eventscript:
9 - CTDB_MONITOR_NFS_THREAD_COUNT
10 - CTDB_NFS_DUMP_STUCK_THREADS
12 See ctdb.sysconfig for details.
17 * ctdb tool should not exit from a retry loop if a control times out
18 (e.g. under high load). This simple fix will stop an exit from the
19 retry loop on any error.
21 * When updating flags on all nodes, use the correct updated flags. This
22 should avoid wrong flag change messages in the logs.
24 * The recovery daemon will not ban other nodes if the current node
27 Important internal changes
28 --------------------------
30 * The recovery daemon on stopped or banned node will stop participating in any
40 * The "stopped" event has been removed.
42 The "ipreallocated" event is now run when a node is stopped. Use
43 this instead of "stopped".
45 * New --pidfile option for ctdbd, used by initscript
47 * The 60.nfs eventscript now uses configuration files in
48 /etc/ctdb/nfs-rpc-checks.d/ for timeouts and actions instead of
49 hardcoding them into the script.
51 * Notification handler scripts can now be dropped into /etc/ctdb/notify.d/.
53 * The NoIPTakeoverOnDisabled tunable has been renamed to
54 NoIPHostOnAllDisabled and now works properly when set on individual
57 * New ctdb subcommand "runstate" prints the current internal runstate.
58 Runstates are used for serialising startup.
63 * The Unix domain socket is now set to non-blocking after the
64 connection succeeds. This avoids connections failing with EAGAIN
65 and not being retried.
67 * Fetching from the log ringbuffer now succeeds if the buffer is full.
69 * Fix a severe recovery bug that can lead to data corruption for SMB clients.
71 * The statd-callout script now runs as root via sudo.
73 * "ctdb delip" no longer fails if it is unable to move the IP.
75 * A race in the ctdb tool's ipreallocate code was fixed. This fixes
76 potential bugs in the "disable", "enable", "stop", "continue",
77 "ban", "unban", "ipreallocate" and "sync" commands.
79 * The monitor cancellation code could sometimes hang indefinitely.
80 This could cause "ctdb stop" and "ctdb shutdown" to fail.
82 Important internal changes
83 --------------------------
85 * The socket I/O handling has been optimised to improve performance.
87 * IPs will not be assigned to nodes during CTDB initialisation. They
88 will only be assigned to nodes that are in the "running" runstate.
90 * Improved database locking code. One improvement is to use a
91 standalone locking helper executable - the avoids creating many
92 forked copies of ctdbd and potentially running a node out of memory.
94 * New control CTDB_CONTROL_IPREALLOCATED is now used to generate
95 "ipreallocated" events.
97 * Message handlers are now indexed, providing a significant
98 performance improvement.