You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously, in the index updater we used the purge_seq value from clouseau. In
some cases that can return an older value (0 on a new index) than what is in
the purge checkpoint doc created in `maybe_create_local_purge_doc/2`. (In that
function we initialize the checkpoint with the db purge sequence and call
`clouseau_rpc:set_purge_seq/1` to also set the clouseau purge seq value). An
older purge sequence than the current minimum db purge sequence would result in
an `invalid_start_purge_seq` being thrown during purged infos folding.
In general, if a client updates a purge checkpoint, then it should not query
purged infos with a sequence value below that, since if that is the lowest
current purge checkpoint value and compaction runs, it could have removed all
the purged infos below that.
0 commit comments