Reset progress counters after compaction per bucket - #226
Merged
Merged
Conversation
rkistner
approved these changes
Oct 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Due to compaction, the
target_countvalue of a bucket can shrink between sync iterations. This breaks client-side progress reports, which are based oncount_since_last_checkpoint / (target_count - old_target_count). We have a check detecting implausibletarget_countvalues which then clears local progress counters.Currently, these counters are reset for all buckets. This leads to underreported progress when a compaction only affects a few buckets. With this PR, we only clear counters for affected buckets.
Closes #225.