| commit | b234ae0a900052b03ca22efab8fa1b9e11f44ecc | |
| author | Martin Schwenke <martin@meltin.net> | |
| Thu, 11 Jun 2015 05:49:25 +0000 (11 15:49 +1000) | ||
| committer | Amitay Isaacs <amitay@samba.org> | |
| Wed, 1 Jul 2015 02:18:28 +0000 (1 04:18 +0200) | ||
| tree | 3f25cdf4bee11764d6019d75029ebd0bdd4d921a | treesnapshot (tar.gz zip) |
| parent | 036c2a92438585ab6b99a22fcf67b67890c525f0 | commitdiff |
ctdb-recoverd: Clear IP assignment tree on election loss
If a node was previously recovery master (say, 20 years ago) and it
becomes recovery master again then, if IP assignments have changed,
verify_remote_ip_allocation() can produce messages like the following
when called during recovery:
ctdbd: recoverd:Inconsistent IP allocation - node 0 thinks 10.1.1.1 is held by node 0 while it is assigned to node 1
When a node loses an election it should clear all data specific to it
being the recovery master.
Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
If a node was previously recovery master (say, 20 years ago) and it
becomes recovery master again then, if IP assignments have changed,
verify_remote_ip_allocation() can produce messages like the following
when called during recovery:
ctdbd: recoverd:Inconsistent IP allocation - node 0 thinks 10.1.1.1 is held by node 0 while it is assigned to node 1
When a node loses an election it should clear all data specific to it
being the recovery master.
Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
| ctdb/server/ctdb_recoverd.c | diffblobblamehistory |