From 1898200481f64676e596e52dc177c8d70ca1a00c Mon Sep 17 00:00:00 2001 From: Michael Adam Date: Fri, 12 Jun 2015 10:59:54 +0200 Subject: [PATCH] ctdb-vacuum: revert "Do not delete VACUUM MIGRATED records immediately" This reverts commit 257311e337065f089df688cbf261d2577949203d. That commit was due to a misunderstanding, and it does not fix what it was supposed to fix. Signed-off-by: Michael Adam Reviewed-by: Amitay Isaacs --- ctdb/server/ctdb_ltdb_server.c | 5 ----- 1 file changed, 5 deletions(-) diff --git a/ctdb/server/ctdb_ltdb_server.c b/ctdb/server/ctdb_ltdb_server.c index 8cf718098e5..c94e1d5c253 100644 --- a/ctdb/server/ctdb_ltdb_server.c +++ b/ctdb/server/ctdb_ltdb_server.c @@ -115,11 +115,6 @@ static int ctdb_ltdb_store_server(struct ctdb_db_context *ctdb_db, * fails. So storing the empty record makes sure that we do not * need to change the client code. */ - if ((header->flags & CTDB_REC_FLAG_VACUUM_MIGRATED) && - (ctdb_db->ctdb->pnn == header->dmaster)) { - keep = true; - schedule_for_deletion = true; - } if (!(header->flags & CTDB_REC_FLAG_VACUUM_MIGRATED)) { keep = true; } else if (ctdb_db->ctdb->pnn != header->dmaster) { -- 2.34.1