From 2ad1c3f6c7e2a574325ab94d29a72e228c1b6e24 Mon Sep 17 00:00:00 2001 From: Michael Adam Date: Fri, 10 Dec 2010 13:59:37 +0100 Subject: server: in the VACUUM_FETCH handler, add the VACUUM_MIGRAION to the call flags This way, the records coming in via this handler, can be treated appropriately. Namely, they can be deleted instead of being stored when the meet the fast-path vacuuming criteria (empty, never migrated with data...) (This used to be ctdb commit fb5d832104970320359b3e474eb291ca3d629380) --- ctdb/server/ctdb_recoverd.c | 1 + 1 file changed, 1 insertion(+) diff --git a/ctdb/server/ctdb_recoverd.c b/ctdb/server/ctdb_recoverd.c index f411dad602..7b5814959f 100644 --- a/ctdb/server/ctdb_recoverd.c +++ b/ctdb/server/ctdb_recoverd.c @@ -714,6 +714,7 @@ static void vacuum_fetch_next(struct vacuum_info *v) ZERO_STRUCT(call); call.call_id = CTDB_NULL_FUNC; call.flags = CTDB_IMMEDIATE_MIGRATION; + call.flags |= CTDB_CALL_FLAG_VACUUM_MIGRATION; r = v->r; v->r = (struct ctdb_rec_data *)(r->length + (uint8_t *)r); -- cgit