summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRonnie Sahlberg <ronniesahlberg@gmail.com>2009-04-02 14:50:43 +1100
committerRonnie Sahlberg <ronniesahlberg@gmail.com>2009-04-02 14:50:43 +1100
commit2393df39893510d130eb36e9eb6a08346e7d82fe (patch)
treea22b94cf14f5936c66a77599f7fdcd6acba55bce
parentd94917ec49690416772686a582085b8f18e6602a (diff)
downloadsamba-2393df39893510d130eb36e9eb6a08346e7d82fe.tar.gz
samba-2393df39893510d130eb36e9eb6a08346e7d82fe.tar.xz
samba-2393df39893510d130eb36e9eb6a08346e7d82fe.zip
if we cant pull the remote nodemap off a node we should mark it as a culprit so it eventually becomes banned.
(This used to be ctdb commit 0889ae3c237bdb3bd72d45f2f64f5e5d8420870c)
-rw-r--r--ctdb/server/ctdb_recoverd.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/ctdb/server/ctdb_recoverd.c b/ctdb/server/ctdb_recoverd.c
index 28be460c98..ef610a37cc 100644
--- a/ctdb/server/ctdb_recoverd.c
+++ b/ctdb/server/ctdb_recoverd.c
@@ -2663,6 +2663,8 @@ again:
if (remote_nodemaps[j] == NULL) {
DEBUG(DEBUG_ERR,(__location__ " Did not get a remote nodemap for node %d, restarting monitoring\n", j));
+ ctdb_set_culprit(rec, j);
+
goto again;
}