summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichael Adam <obnox@samba.org>2010-12-10 13:59:37 +0100
committerMichael Adam <obnox@samba.org>2011-03-14 13:35:44 +0100
commit2ad1c3f6c7e2a574325ab94d29a72e228c1b6e24 (patch)
treeca2a0e6770d3c97fc2b62aacba8380043c401a85
parentf7eeb42219d06788485907052180a462de4699d7 (diff)
downloadsamba-2ad1c3f6c7e2a574325ab94d29a72e228c1b6e24.tar.gz
samba-2ad1c3f6c7e2a574325ab94d29a72e228c1b6e24.tar.xz
samba-2ad1c3f6c7e2a574325ab94d29a72e228c1b6e24.zip
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)
-rw-r--r--ctdb/server/ctdb_recoverd.c1
1 files changed, 1 insertions, 0 deletions
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);