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>

diff --git a/server/ctdb_recover.c b/server/ctdb_recover.c
index 6506f8bbce3be119845345a0537f2a04fcfc561f..7a8b0bb1018aec37ead36b5e7d3581adef212b2c 100644 (file)
--- a/server/ctdb_recover.c
+++ b/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;
        }