[jira] [Updated] (CASSANDRA-19287) Accord: Ensure no storage timestamp clashes across Accord bootstrap

["Benedict Elliott Smith (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-19287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benedict Elliott Smith updated CASSANDRA-19287:
-----------------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Triage Needed)

> Accord: Ensure no storage timestamp clashes across Accord bootstrap
> -------------------------------------------------------------------
>
>                 Key: CASSANDRA-19287
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19287
>             Project: Apache Cassandra
>          Issue Type: Improvement
>          Components: Accord
>            Reporter: Benedict Elliott Smith
>            Priority: Normal
>
> At present bootstrap does not propagate the local metadata associated with the shard that is being bootstrapped. However, due to the many-to-one relation between Accord timestamps and sstable/C* timestamps it is possible for transactions with the same sstable timestamp to occur either side of a bootstrap for a single key. We can resolve this by either
>  # Propagating the timestamp state from Accord system tables alongside bootstrap
>  # Making the relationship between timestamps 1:1, by
>  ** assigning each replica in the cluster a range of timestamps to allocate for Accord transactions
>  ** permit timestamps larger than 8 bytes
>  # Prevent timestamp clashes across a SyncPoint



--
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