| commit | 90a96f06a938d5fdae33c959c71103add3064b96 | |
| author | Martin Schwenke <martin@meltin.net> | |
| Thu, 19 May 2022 05:09:41 +0000 (19 15:09 +1000) | ||
| committer | Amitay Isaacs <amitay@samba.org> | |
| Tue, 31 May 2022 05:06:29 +0000 (31 05:06 +0000) | ||
| tree | 95ce70055cfc4e9a695d7ce87f321180a193e1d7 | treesnapshot (tar.gz zip) |
| parent | a400f4e7cc0f48efd7b88354d1a550615fec6d64 | commitdiff |
ctdb-recoverd: Do not ban on unknown error when taking cluster lock
If the cluster filesystem is unavailable then I/O errors may occur.
This is no worse than contention, so don't ban. This avoids having
services unavailable for longer than necessary.
Update the associated test to simply confirm that this results in a
leaderless cluster, and leadership is restored when the lock can once
again be taken.
Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
If the cluster filesystem is unavailable then I/O errors may occur.
This is no worse than contention, so don't ban. This avoids having
services unavailable for longer than necessary.
Update the associated test to simply confirm that this results in a
leaderless cluster, and leadership is restored when the lock can once
again be taken.
Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
| ctdb/server/ctdb_recoverd.c | diffblobblamehistory | |
| ctdb/tests/INTEGRATION/simple/cluster.016.reclock_move_lock_dir.sh | diffblobblamehistory |