From a002c6ec1264b4bd4e600db0c914a6729b371556 Mon Sep 17 00:00:00 2001 From: Amitay Isaacs Date: Fri, 24 May 2013 18:07:39 +1000 Subject: vacuum: Reduce the priority of non-critical error Since the complete database is not locked when the receive_records control is received, it's possible that we may not be able to obtain lock on a chain. We will try again to store this record. Signed-off-by: Amitay Isaacs Reviewed-by: Michael Adam (This used to be ctdb commit 32723c9efdad1c6ca4aa53f308ccd9bef1aadfff) --- ctdb/server/ctdb_recover.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ctdb/server/ctdb_recover.c b/ctdb/server/ctdb_recover.c index 6506f8bbce..7a8b0bb101 100644 --- a/ctdb/server/ctdb_recover.c +++ b/ctdb/server/ctdb_recover.c @@ -1138,7 +1138,7 @@ static int store_tdb_record(struct ctdb_context *ctdb, /* use a non-blocking lock */ if (tdb_chainlock_nonblock(ctdb_db->ltdb->tdb, key) != 0) { - DEBUG(DEBUG_ERR, (__location__ " Failed to lock chain\n")); + DEBUG(DEBUG_INFO, (__location__ " Failed to lock chain in non-blocking mode\n")); return -1; } -- cgit