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 <amitay@gmail.com>
Reviewed-by: Michael Adam <obnox@samba.org>
(cherry picked from commit 32723c9efdad1c6ca4aa53f308ccd9bef1aadfff)

diff --git a/server/ctdb_recover.c b/server/ctdb_recover.c
index 4794e638d1a52a4e66aec9c348d8a08ad9cc0cca..ed6fe414ab4fe51dcf8e867ceff1f09f1be92190 100644 (file)
--- a/server/ctdb_recover.c
+++ b/server/ctdb_recover.c
@@ -1120,7 +1120,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;
        }