[ https://issues.apache.org/jira/browse/CASSANDRA-8272 ]
Manish Khandelwal deleted comment on CASSANDRA-8272:
----------------------------------------------
was (Author: manmagic3):
Hi, reading the comments on this ticket indicates a performance hit for people
using queries with "ALLOW FILTERING" with CL above One or Local_ONE. But I see
this ticket fixed in Cassandra 3.11.7. When I upgraded to Cassandra 3.11.13, I
did not see the dip in performance but after upgrading to Cassandra 4.0.x , I
am seeing test cases using "ALLOW FILTERING" with CL LOCAL_QUORUM taking a hit.
Is there something which only went in Cassandra 4.0.x and not in 3.11.7+.
> 2ndary indexes can return stale data
> ------------------------------------
>
> Key: CASSANDRA-8272
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8272
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/2i Index
> Reporter: Sylvain Lebresne
> Assignee: Andres de la Peña
> Priority: Normal
> Labels: pull-request-available
> Fix For: 3.0.21, 3.11.7, 4.0-beta1, 4.0
>
> Time Spent: 7h
> Remaining Estimate: 0h
>
> When replica return 2ndary index results, it's possible for a single replica
> to return a stale result and that result will be sent back to the user,
> potentially failing the CL contract.
> For instance, consider 3 replicas A, B and C, and the following situation:
> {noformat}
> CREATE TABLE test (k int PRIMARY KEY, v text);
> CREATE INDEX ON test(v);
> INSERT INTO test(k, v) VALUES (0, 'foo');
> {noformat}
> with every replica up to date. Now, suppose that the following queries are
> done at {{QUORUM}}:
> {noformat}
> UPDATE test SET v = 'bar' WHERE k = 0;
> SELECT * FROM test WHERE v = 'foo';
> {noformat}
> then, if A and B acknowledge the insert but C respond to the read before
> having applied the insert, then the now stale result will be returned (since
> C will return it and A or B will return nothing).
> A potential solution would be that when we read a tombstone in the index (and
> provided we make the index inherit the gcGrace of it's parent CF), instead of
> skipping that tombstone, we'd insert in the result a corresponding range
> tombstone.
--
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
