mirror of
https://github.com/samba-team/samba.git
synced 2025-02-28 01:58:17 +03:00
fdccaab2a9
"monitor" events can be cancelled. If a reconfigure action does a service restart then the "monitor" event can be cancelled at the inconvenient moment after the service is stopped. In this case the service stays down and the node may become unhealthy (depending on whether there are any repair actions in the monitor event). A long time ago we did service reconfiguration in "monitor" events following failovers. Service reconfiguration was then moved to the "ipreallocated" event. However, reconfiguration in "monitor" events has been kept as a last resort in case an "ipreallocate" event does not occur. The only important case that this covers is "ctdb deleteip", where "releaseip" events are generated without a corresponding "ipreallocated". Therefore, IPs can be deleted without running the required service reconfiguration. The supported way of removing IP addresses is now via "ctdb reloadips", which always causes a takeover run with a corresponding "ipreallocate" event. This means that service reconfiguration in "monitor" events is no longer required and should be removed because it is unsafe. Also update the associated tests. Make the first confirm that the monitor event no longer does reconfiguration. Change the others to test that monitor status is correctly replayed when something else is doing a reconfigure and currently holds the reconfigure lock. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com> Autobuild-User(master): Amitay Isaacs <amitay@samba.org> Autobuild-Date(master): Tue Dec 17 06:32:35 CET 2013 on sn-devel-104
This directory contains run-time support scripts for CTDB.
Selected highlights:
ctdb.init
An initscript for starting ctdbd at boot time.
events.d/
Eventscripts. See events.d/README for more details.
functions
Support functions, sourced by eventscripts and other scripts.
statd-callout
rpc.statd high-availability callout to support lock migration on
failover.
Notes:
* All of these scripts are written in POSIX Bourne shell. Please
avoid bash-isms, including the use of "local" variables (which are
not available in POSIX shell).
* Do not use absolute paths for commands. Unit tests attempt to
replace many commands with stubs and can not do this if commands are
specified with absolute paths. The functions file controls $PATH so
absolute paths should not be required.