| commit | 57310f80c9b8146a0978d912f73b0a64fde7697e | |
| author | Amitay Isaacs <amitay@gmail.com> | |
| Thu, 25 Sep 2014 07:17:04 +0000 (25 17:17 +1000) | ||
| committer | Martin Schwenke <martins@samba.org> | |
| Thu, 25 Sep 2014 12:48:11 +0000 (25 14:48 +0200) | ||
| tree | 429534bda7eb2acf641321b8143a753cabd34098 | treesnapshot (tar.gz zip) |
| parent | f1e281cd47d9ebd79e09294606b8fa411ec0fbb4 | commitdiff |
ctdb-recoverd: If obtaining recovery lock fails, try again
When ctdb daemon starts up, it considers itself the recovery master
and tries to do first recovery. However, it's possible that there is
already a recovery master and the current node has not yet heard from it.
So do not ban ourselves immediately if ctdb_recovery_lock() fails when
doing first recovery.
Signed-off-by: Amitay Isaacs <amitay@gmail.com>
Reviewed-by: Martin Schwenke <martin@meltin.net>
When ctdb daemon starts up, it considers itself the recovery master
and tries to do first recovery. However, it's possible that there is
already a recovery master and the current node has not yet heard from it.
So do not ban ourselves immediately if ctdb_recovery_lock() fails when
doing first recovery.
Signed-off-by: Amitay Isaacs <amitay@gmail.com>
Reviewed-by: Martin Schwenke <martin@meltin.net>
| ctdb/server/ctdb_recoverd.c | diffblobblamehistory |