storage: gc range tombstone - fix mvcc stat update on merge #87408
Conversation
This file contains 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
Previously if range tombstone fragment was not eligible for GC it was not checked if it can merge with previous range tombstone fragments stack. This was causing MVCC stats discrepancy. This commit adds a check merge eligibility check for skipped fragments. Release justification: bugfix for upcoming functionality Release note: None
|
This change is |
erikgrinaker
approved these changes
Sep 6, 2022
tbg
approved these changes
Sep 6, 2022
|
bors r+ |
|
Build succeeded: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previously if range tombstone fragment was not eligible for GC
it was not checked if it can merge with previous range tombstone
fragments stack. This was causing MVCC stats discrepancy.
This commit adds a check merge eligibility check for skipped
fragments.
Release justification: bugfix for upcoming functionality
Release note: None
Fixes: #87406