[
https://issues.apache.org/jira/browse/CASSANDRA-19436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17820826#comment-17820826
]
Ariel Weisberg commented on CASSANDRA-19436:
--------------------------------------------
This issue covers detecting and generating the appropriate refusal to accept a
read/write on the wrong system. Accord and Paxos already do this detection, but
non-SERIAL operations do not.
The linked issues cover this, but also the loop in read/write that receives the
error and automatically retries instead of failing the query.
> When transitioning to Accord migration it's not safe to read immediately
> using Accord due to concurrent non-serial writes
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-19436
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19436
> Project: Cassandra
> Issue Type: Bug
> Reporter: Ariel Weisberg
> Priority: Normal
>
> Concurrent writes at the same time that migration starts make it unsafe to
> read from Accord because txn recovery will not be deterministic in the
> presences of writes not done through Accord.
> Adding key migration to non-serial writes could solve this by causing writes
> not going through Accord to be rejected at nodes where key migration already
> occurred.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
