ctdb-daemon: Drop the "schedule for deletion" messages to DEBUG level

Thousands of these can be generated each second, rendering INFO level debugging useless. Signed-off-by: Martin Schwenke <[email protected]> Reviewed-by: Michael Adam <[email protected]>
darabosj · Jan 12, 2016 · 8f73ae0 · 8f73ae0
1 parent 9790abd
commit 8f73ae0
Showing 1 changed file with 5 additions and 5 deletions.
diff --git a/ctdb/server/ctdb_vacuum.c b/ctdb/server/ctdb_vacuum.c
@@ -1659,11 +1659,11 @@ static int insert_record_into_delete_queue(struct ctdb_db_context *ctdb_db,
 
 	hash = (uint32_t)ctdb_hash(&key);
 
-	DEBUG(DEBUG_INFO, (__location__ " schedule for deletion: db[%s] "
-			   "db_id[0x%08x] "
-			   "key_hash[0x%08x] "
-			   "lmaster[%u] "
-			   "migrated_with_data[%s]\n",
+	DEBUG(DEBUG_DEBUG, (__location__ " schedule for deletion: db[%s] "
+			    "db_id[0x%08x] "
+			    "key_hash[0x%08x] "
+			    "lmaster[%u] "
+			    "migrated_with_data[%s]\n",
 			    ctdb_db->db_name, ctdb_db->db_id,
 			    hash,
 			    ctdb_lmaster(ctdb_db->ctdb, &key),