[C++] Guard against empty compaction ranges #947
Draft
Conversation
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
1 participant
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, compaction could stall indefinitely if the provided
until_addresswas equal tohlog.begin_address. This could occur, if called from an existing test whenauto_compactionisfalse. In this case,pages_availableremained permanentlytrue, causing compaction threads to spin and preventingLightEpochfrom draining pending GC callbacks (as reported in #944).The changes in this PR ensure we validate the compaction range upfront (
until_address>hlog.begin_address). If the range is invalid, we now skip compaction. When the call originates from theF2Kvclass, a warning is logged before skipping.