(release/v1.6) Compaction: Expired keys and delete markers are never purged (#1354) #1510
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.
The compaction process accidentally keeps one more version of
expired keys and delete markers than it should, because of
logic error in *levelsController.compactBuildTables(). When
NumVersionsToKeep is 1, it means that expired keys and delete
markers are never actually purged from the LSM tables.
Co-authored-by: Julian Hegler julian.hegler@tanium.com
Co-authored-by: Ibrahim Jarif ibrahim@dgraph.io
(cherry picked from commit fd89894)
This cherry-pick PR had conflicts.
This change is![Reviewable](https://camo.githubusercontent.com/1541c4039185914e83657d3683ec25920c672c6c5c7ab4240ee7bff601adec0b/68747470733a2f2f72657669657761626c652e696f2f7265766965775f627574746f6e2e737667)