| commit | e77d5f99e396d71c1d354b3f8dc5ddf9ba5c5ee9 | |
| author | Martin Schwenke <martin@meltin.net> | |
| Wed, 18 Dec 2013 08:15:39 +0000 (18 19:15 +1100) | ||
| committer | Amitay Isaacs <amitay@gmail.com> | |
| Fri, 17 Jan 2014 06:59:19 +0000 (17 17:59 +1100) | ||
| tree | c7b53b1116c5ac408462ca8ccd6070f9c540a6dd | treesnapshot (tar.gz zip) |
| parent | a955d0bedce888597633c0c88082f29e1d26e503 | commitdiff |
ctdb/recoverd: Do not refuse disabling takeover runs on inactive nodes
Failure might be expected when disabling takeover runs on banned
nodes, since they might be suffering from performance problems or
similar. More broadly, administrators who reconfigure a cluster that
isn't in a happy state aren't necessarily doing something sensible.
However, allowing takeover runs to be disabled on inactive nodes stops
reconfiguration of stopped nodes. This is probaby an unreasonable
limitation, so drop it.
Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
Failure might be expected when disabling takeover runs on banned
nodes, since they might be suffering from performance problems or
similar. More broadly, administrators who reconfigure a cluster that
isn't in a happy state aren't necessarily doing something sensible.
However, allowing takeover runs to be disabled on inactive nodes stops
reconfiguration of stopped nodes. This is probaby an unreasonable
limitation, so drop it.
Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
| ctdb/server/ctdb_recoverd.c | diffblobblamehistory |