[
https://issues.apache.org/jira/browse/CASSANDRA-20489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-20489:
----------------------------------------
Fix Version/s: 5.1-alpha1
(was: 5.x)
Since Version: 5.1-alpha1
Source Control Link:
https://github.com/apache/cassandra/commit/b31d15b9b58926676436807ddc1efdd5616e13b3
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Avoid failing queries when epoch changes and replica goes up/down
> -----------------------------------------------------------------
>
> Key: CASSANDRA-20489
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20489
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Priority: Normal
> Fix For: 5.1-alpha1
>
> Attachments: ci_summary.html
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> To make sure that we got responses from the correct replicas we recompute the
> replica plan for queries if the epoch changes during the query to make sure
> we got responses from a quorum of the nodes in the recomputed replica plan.
> Problem is that this recomputation is filtering away down nodes, so we can
> fail queries if the coordinator marks a replica down during the query and the
> epoch changes, even though the placements have not changed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
