[
https://issues.apache.org/jira/browse/CASSANDRA-18407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-18407:
----------------------------------------
Change Category: Semantic
Complexity: Normal
Component/s: Transactional Cluster Metadata
Reviewers: Alex Petrov, Marcus Eriksson
Status: Open (was: Triage Needed)
https://github.com/beobal/cassandra/commit/601d56ac36e74ddaa28ac6dcbbfc3764f8961c4c
> CEP-21 Remove paranoid check which fails due to pre-existing mismatch on
> replica vs query range
> -----------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-18407
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18407
> Project: Cassandra
> Issue Type: Improvement
> Components: Transactional Cluster Metadata
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Normal
>
> If short read protection is activated, a replica plan is constructed to fetch
> additional partitions from a single replica in the original set. As
> additional partitions are requested, the data range of the query is reduced
> but the original \{{Replica}} instance is reused, resulting in a mismatch
> between the range of the query and that of the replica. This is not new to
> TCM and is present in trunk. It is called out in a comment, but thought to be
> harmless as the narrowed range should be a subset of the original data range
> which did match the replica's. Early TCM patches introduced an addition check
> here on the two ranges and so rejects SRP queries which trunk does not.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
