diff options
| author | Martin Schwenke <martin@meltin.net> | 2019-08-19 21:52:57 +1000 |
|---|---|---|
| committer | Karolin Seeger <kseeger@samba.org> | 2019-08-28 09:12:17 +0000 |
| commit | a93c591a11a9b19f4f5df87c76e3b2f3f7404339 (patch) | |
| tree | 039c12cf84869d794ae754fad7ec4b1bda183ecc /ctdb | |
| parent | 093973899580c2fd1a95d067ff695388b7bdc4f8 (diff) | |
| download | samba-a93c591a11a9b19f4f5df87c76e3b2f3f7404339.tar.gz | |
ctdb-daemon: Switch banning code to use ctdb_node_become_inactive()
There's no reason to avoid immediately setting recovery mode to active
and initiating freeze of databases.
This effectively reverts the following commits:
d8f3b490bbb691c9916eed0df5b980c1aef23c85
b4357a79d916b1f8ade8fa78563fbef0ce670aa9
The latter is now implemented using a control, resulting in looser
coupling.
See also the following commit:
f8141e91a693912ea1107a49320e83702a80757a
BUG: https://bugzilla.samba.org/show_bug.cgi?id=14087
Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
(cherry picked from commit 0f5f7b7cf4e970f3f36c5e0b3d09e710fe90801a)
Diffstat (limited to 'ctdb')
| -rw-r--r-- | ctdb/server/ctdb_banning.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/ctdb/server/ctdb_banning.c b/ctdb/server/ctdb_banning.c index 9cd163645a1..11794dc5b0b 100644 --- a/ctdb/server/ctdb_banning.c +++ b/ctdb/server/ctdb_banning.c @@ -129,7 +129,7 @@ int32_t ctdb_control_set_ban_state(struct ctdb_context *ctdb, TDB_DATA indata) ctdb_ban_node_event, ctdb); if (!already_banned) { - ctdb_local_node_got_banned(ctdb); + ctdb_node_become_inactive(ctdb); } return 0; } |