[ https://issues.apache.org/jira/browse/CASSANDRA-13423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984566#comment-15984566 ]
Andrés de la Peña commented on CASSANDRA-13423: ----------------------------------------------- This could probably be solved by [CASSANDRA-8272|https://issues.apache.org/jira/browse/CASSANDRA-8272]. > Secondary indexes can return stale data for deleted rows in 2.x > --------------------------------------------------------------- > > Key: CASSANDRA-13423 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13423 > Project: Cassandra > Issue Type: Bug > Reporter: Benjamin Lerer > Assignee: Andrés de la Peña > > In {{2.x}} when the secondary index detect that a row has been deleted it > removes it from the index. This approach can result in stale data being > returned if one of the nodes has not yet received the deletion. > The problem come from this > {{line|https://github.com/apache/cassandra/blob/cassandra-2.1/src/java/org/apache/cassandra/db/index/composites/CompositesSearcher.java#L284}}. > > To avoid that problem we should remove the rows from the indexes only once > they has been garbage collected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)