[
https://issues.apache.org/jira/browse/CASSANDRA-18456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713523#comment-17713523
]
Sam Tunnicliffe commented on CASSANDRA-18456:
---------------------------------------------
https://github.com/beobal/cassandra/commit/b2b08d8e21f20576148d8c9602401d6d9f7193b4
> 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
>
> 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]
