Fix CompactRange with kForceOptimized in range split scenarios (#12702) #14113
+109
−5
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.
Summary:
Fix a bug where CompactRange with BottommostLevelCompaction::kForceOptimized would incorrectly return early when two conditions occurred simultaneously:
Root Cause:
The original code at line 784 would return nullptr immediately when inputs_shrunk was empty, without checking if covering_the_whole_range was false (indicating more files beyond the size limit).
The Fix:
Set compaction_end to signal the caller to continue with remaining files when the two conditions are met
Fixes #12702
Test Plan:
make db_compaction_test
./db_compaction_test --gtest_filter="DBCompactionTest.ManualCompactionBottomLevelOptimized"