[
https://issues.apache.org/jira/browse/CASSANDRA-18456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-18456:
----------------------------------------
Fix Version/s: NA
Source Control Link:
https://github.com/apache/cassandra/commit/55bdbcde6e3d75cfb6371ead0733b3ce8a376797
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> CEP-21 During startup request replay from CMS asynchronously
> ------------------------------------------------------------
>
> Key: CASSANDRA-18456
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18456
> Project: Cassandra
> Issue Type: Improvement
> Components: Transactional Cluster Metadata
> Reporter: Sam Tunnicliffe
> Assignee: Marcus Eriksson
> Priority: Normal
> Fix For: NA
>
>
> During the startup sequence, nodes first replay any locally persisted
> metadata changes then request any newer, unseen updates from the CMS. This
> second part should be both async and optional, meaning a CMS failure or
> partition shouldn't prevent nodes from starting up.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
