| commit | d340f308e76af53b04ae9b5432c4f6c84315303a | |
| author | Martin Schwenke <martin@meltin.net> | |
| Tue, 10 Feb 2015 04:43:03 +0000 (10 15:43 +1100) | ||
| committer | Amitay Isaacs <amitay@samba.org> | |
| Tue, 7 Apr 2015 05:43:13 +0000 (7 07:43 +0200) | ||
| tree | 891ef6e9b1654cbcacb39617708b211e01f81bbf | treesnapshot (tar.gz zip) |
| parent | 85bd9a33eb65d6fd03ad85aeedf141a2813c2bb8 | commitdiff |
ctdb-daemon: Don't delay reloading the nodes file
Presumably this was done to minimise the chance of a recovery
occurring while the nodemaps are inconsistent across nodes.
Another potential theory is that the forced recovery in the
ctdb.c:control_reload_nodes_file() stops another recovery occurring
for ReRecoveryTimeout seconds, so this delay causes the reloads to
occur during that period.
This is no longer necessary because recoveries are now explicitly
disabled while node files are reloaded.
Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
Presumably this was done to minimise the chance of a recovery
occurring while the nodemaps are inconsistent across nodes.
Another potential theory is that the forced recovery in the
ctdb.c:control_reload_nodes_file() stops another recovery occurring
for ReRecoveryTimeout seconds, so this delay causes the reloads to
occur during that period.
This is no longer necessary because recoveries are now explicitly
disabled while node files are reloaded.
Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
| ctdb/server/ctdb_recover.c | diffblobblamehistory |