git.samba.org / amitay / ctdb.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: a17316a) | patch
Eventscripts: "recovered" event should not fail on NATGW failure
authorMartin Schwenke <martin@meltin.net>
Wed, 26 Sep 2012 04:37:49 +0000 (14:37 +1000)
committerAmitay Isaacs <amitay@gmail.com>
Tue, 2 Oct 2012 00:31:01 +0000 (10:31 +1000)
commite62756004d3c61696ffd706442bf9cbfcfbf41f5
tree97b32f1f2d3c62606a1de29cf3fd158d2566d648tree
parenta17316ab3a5ee3cd748b26863c55e82937edf013commit | diff
Eventscripts: "recovered" event should not fail on NATGW failure

The recovery process has no protection against the "recovered" event
failing, so this can cause a recovery loop.

Instead of failing the "recovered" event, add a "monitor" event and
fail that instead.  In this case the failure semantics are well
defined.

A separate patch should ban nodes if the "recovered" event fails for
an unknown reason.

Signed-off-by: Martin Schwenke <martin@meltin.net>
config/events.d/11.natgw diff | blob | history
Amitay's CTDB development