[
https://issues.apache.org/jira/browse/CASSANDRA-19439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ariel Weisberg updated CASSANDRA-19439:
---------------------------------------
Attachment: cep-15-accord.html
> Non-serial reads need to handle racing with Accord topology changes
> -------------------------------------------------------------------
>
> Key: CASSANDRA-19439
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19439
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Accord
> Reporter: Ariel Weisberg
> Assignee: Ariel Weisberg
> Priority: Normal
> Attachments: cep-15-accord.html, ci_summary.html
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> A key or range read could end up being sent to Accord when it's not managed
> by Accord and we might not find out until the execution epoch is known. In
> reality I think this already throws an exception in Accord for a key we just
> need to propagate and handle the exception and retry with the new topology
> until we can complete the read.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
