You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Laxmikant Upadhyay (JIRA)" <ji...@apache.org> on 2019/06/14 05:16:00 UTC
[jira] [Commented] (CASSANDRA-15159) Purgable tombstones are
ignored by read query
[ https://issues.apache.org/jira/browse/CASSANDRA-15159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16863699#comment-16863699 ]
Laxmikant Upadhyay commented on CASSANDRA-15159:
------------------------------------------------
This issue is not related to CASSANDRA-12765 as the sstable with tombstone does not have maxLocalDeletionTime == Integer.MAX_VALUE.
> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org