You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ariel Weisberg (Jira)" <ji...@apache.org> on 2025/01/27 21:52:00 UTC
[jira] [Assigned] (CASSANDRA-19439) Non-serial reads need to handle racing with Accord topology changes
[ https://issues.apache.org/jira/browse/CASSANDRA-19439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ariel Weisberg reassigned CASSANDRA-19439:
------------------------------------------
Assignee: Ariel Weisberg
> 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
> Reporter: Ariel Weisberg
> Assignee: Ariel Weisberg
> Priority: Normal
>
> 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org