[
https://issues.apache.org/jira/browse/CASSANDRA-15159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18016473#comment-18016473
]
Michael Semb Wever commented on CASSANDRA-15159:
------------------------------------------------
I can reproduce this on 5.0.5
Missing from steps2reproduce.txt is the steps to (on all nodes)
nodetool disablehandoff
nodetool disableautocompaction
And lowering GC_GRACE_SECONDS on the table isn't required.
Also note, results are correct when the coordinator is node3 (where the
tombstone isn't locally).
bq. I don't see this as a bug.
[~benkrug], it's a bug. this isn't about tombstones resurrecting. the correct
behaviour should be no results.
> Purgable tombstones are ignored by read query
> ---------------------------------------------
>
> Key: CASSANDRA-15159
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15159
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths
> Reporter: Laxmikant Upadhyay
> Priority: Normal
> Attachments: steps2reproduce.txt, trace.txt
>
>
> In 3 node Cassandra cluster, one node has old mutation and two nodes have
> evict-able (crossed gc grace period) tombstone produced by TTL. A read query
> with local quorum return the old mutation as result when one request goes to
> the node having old mutation. However expected result should be empty.
> Attached the steps to reproduce and trace of read query.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
