From cb94eba157679574c05d85f05828195e4099f2ba Mon Sep 17 00:00:00 2001 From: Martin Schwenke Date: Fri, 25 Jul 2014 16:56:57 +1000 Subject: ctdb-eventscripts: Remove NAT gateway "monitor" event This event was introduced to handle misconfiguration. For example, where all nodes where configured as NAT gateway slaves. However, this event can fail when there are performance issues and capabilities can't be retrieved from a remote node. The problem is most likely with the remote node, so marking the local node UNHEALTHY is probably a mistake. Having a NAT gateway master node only matters in "ipreallocated", so leave it to do the checking. Given that a node will run "ipreallocated" as part of the first recovery, this should cause misconfigurations to be detected nice and early. Signed-off-by: Martin Schwenke Reviewed-by: Amitay Isaacs --- ctdb/config/events.d/11.natgw | 6 ------ ctdb/tests/eventscripts/11.natgw.002.sh | 2 +- ctdb/tests/eventscripts/11.natgw.003.sh | 2 +- ctdb/tests/eventscripts/11.natgw.004.sh | 2 +- ctdb/tests/eventscripts/11.natgw.005.sh | 2 +- 5 files changed, 4 insertions(+), 10 deletions(-) diff --git a/ctdb/config/events.d/11.natgw b/ctdb/config/events.d/11.natgw index f925d4b735..a541d31957 100755 --- a/ctdb/config/events.d/11.natgw +++ b/ctdb/config/events.d/11.natgw @@ -163,12 +163,6 @@ case "$1" in natgw_clear ;; - monitor) - natgw_check_config - natgw_set_capability - natgw_ensure_master "$1" - ;; - *) ctdb_standard_event_handler "@" ;; diff --git a/ctdb/tests/eventscripts/11.natgw.002.sh b/ctdb/tests/eventscripts/11.natgw.002.sh index e496e4a3c4..c9054068df 100755 --- a/ctdb/tests/eventscripts/11.natgw.002.sh +++ b/ctdb/tests/eventscripts/11.natgw.002.sh @@ -18,7 +18,7 @@ required_result 1 <