[
https://issues.apache.org/jira/browse/CASSANDRA-21163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Lightfoot updated CASSANDRA-21163:
--------------------------------------
Description:
[https://pre-ci.cassandra.apache.org/job/cassandra/347/testReport/junit/org.apache.cassandra.db.compaction.simple/CompactionDeleteRowRangeTest/Tests___test_jdk11_2_20___test2DeleteRangeWithOverlapingBoundAndSameTimestampCompaction__jdk11_x86_64/]
[https://pre-ci.cassandra.apache.org/job/cassandra/351/testReport/junit/org.apache.cassandra.db.compaction.simple/CompactionDeleteRowRangeTest/Tests___test_jdk11_2_20___test2DeleteRangeWithOverlapingBoundAndSameTimestampCompaction__jdk11_x86_64/]
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.
was:
[butler link
|https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/org.apac[…]o.sstable/VerifyTest/testVerifyCorruptRowCorrectDigest]
this test looks like has an explicit breaking point + it fails only for
compression config profile +
https://ci-cassandra.apache.org/job/Cassandra-trunk/2367/
so an issue could be between
https://github.com/apache/cassandra/commit/ec3b425c38d92d20d77d3a87c782ed9c072e1cd9
(exclusive) and
https://github.com/apache/cassandra/commit/3c69bd23673caa40b22f3500a3e3eecabc25c8e5
commits
!image-2026-01-31-16-46-01-322.png|width=600!
> Test failure:
> org.apache.cassandra.db.compaction.simple.CompactionDeleteRowRangeTest#test2DeleteRangeWithOverlapingBoundAndSameTimestampCompaction
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-21163
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21163
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Local/SSTable
> Reporter: Sam Lightfoot
> Assignee: Arvind Kandpal
> Priority: Normal
> Fix For: 5.x
>
>
> [https://pre-ci.cassandra.apache.org/job/cassandra/347/testReport/junit/org.apache.cassandra.db.compaction.simple/CompactionDeleteRowRangeTest/Tests___test_jdk11_2_20___test2DeleteRangeWithOverlapingBoundAndSameTimestampCompaction__jdk11_x86_64/]
> [https://pre-ci.cassandra.apache.org/job/cassandra/351/testReport/junit/org.apache.cassandra.db.compaction.simple/CompactionDeleteRowRangeTest/Tests___test_jdk11_2_20___test2DeleteRangeWithOverlapingBoundAndSameTimestampCompaction__jdk11_x86_64/]
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
