[ https://issues.apache.org/jira/browse/CASSANDRA-15159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16868314#comment-16868314 ]
Laxmikant Upadhyay commented on CASSANDRA-15159: ------------------------------------------------ Thanks [~eperott] for your analysis. You are right, it is annoying and getting resurrected data in this condition seems a violation of "last write wins" rule. However replicating old mutation during the read repair again looks an issue explained by your. > Purgable tombstones are ignored by read query > --------------------------------------------- > > Key: CASSANDRA-15159 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15159 > Project: 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 (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org