CASSANDRA-21163 - Fix flaky test2DeleteRangeWithOverlapingBoundAndSameTimestampCompaction #4608
+12
−4
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
The two deletes use the same CQL timestamp, so compaction should merge their overlapping range tombstones into a single open/close pair (no boundary markers). However, DeletionTime also includes local_delete_time (wall-clock seconds), which may differ between deletes if a second boundary is crossed during the flush. Differing local_delete_time causes the merger to treat them as distinct deletions, producing boundary markers instead. Using executeInternalWithNowInSec with a fixed nowInSec ensures both deletes get identical DeletionTime values.
samueldlightfoot
changed the title
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.
Test: CompactionDeleteRowRangeTest::test2DeleteRangeWithOverlapingBoundAndSameTimestampCompaction
The two deletes use the same CQL timestamp, so compaction should merge their overlapping range tombstones into a single open/close pair (no boundary markers). However, DeletionTime also includes local_delete_time (wall-clock seconds), which may differ between deletes if a second boundary is crossed during the flush. Differing local_delete_time causes the merger to treat them as distinct deletions, producing boundary markers instead. Using executeInternalWithNowInSec with a fixed nowInSec ensures both deletes get identical DeletionTime values.
patch by Sam Lightfoot; reviewed by for CASSANDRA-21163