cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua McKenzie (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CASSANDRA-13423) Secondary indexes can return stale data for deleted rows in 2.x
Date Mon, 10 Apr 2017 13:09:41 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-13423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Joshua McKenzie reassigned CASSANDRA-13423:
-------------------------------------------

    Assignee: Andrés de la Peña

> 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)

Mime
View raw message