diff options
| author | Amitay Isaacs <amitay@gmail.com> | 2014-05-06 14:24:52 +1000 |
|---|---|---|
| committer | Martin Schwenke <martins@samba.org> | 2014-07-07 13:29:49 +0200 |
| commit | 28a1b75886fb4aea65e23bfd00b9f4c98780fdfd (patch) | |
| tree | 3976171952276426c7b0cc0c4481cdf6bbfa3228 /ctdb/server/ctdb_banning.c | |
| parent | 72c6500ee440779819b9adb768a7022cc251f07e (diff) | |
| download | samba-28a1b75886fb4aea65e23bfd00b9f4c98780fdfd.tar.gz | |
ctdb-recoverd: Set recovery mode before freezing databases
Setting recovery mode to active is the only correct way to inform recovery
daemon to run database recovery. Only freezing databases without setting
recovery mode should not trigger database recovery, as this mechanism
is used in tool to implement wipedb/restoredb commands.
Signed-off-by: Amitay Isaacs <amitay@gmail.com>
Reviewed-by: Martin Schwenke <martin@meltin.net>
Diffstat (limited to 'ctdb/server/ctdb_banning.c')
| -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 13d97c84b13..a9d18910a06 100644 --- a/ctdb/server/ctdb_banning.c +++ b/ctdb/server/ctdb_banning.c @@ -70,11 +70,11 @@ void ctdb_local_node_got_banned(struct ctdb_context *ctdb) */ ctdb->vnn_map->generation = INVALID_GENERATION; + ctdb->recovery_mode = CTDB_RECOVERY_ACTIVE; for (i=1; i<=NUM_DB_PRIORITIES; i++) { ctdb_start_freeze(ctdb, i); } ctdb_release_all_ips(ctdb); - ctdb->recovery_mode = CTDB_RECOVERY_ACTIVE; } int32_t ctdb_control_set_ban_state(struct ctdb_context *ctdb, TDB_DATA indata) |