[jira] [Commented] (CASSANDRA-21036) Better support for CMS initialization when DOWN nodes have not been upgraded

["Sam Tunnicliffe (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-21036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18039655#comment-18039655 ] 

Sam Tunnicliffe commented on CASSANDRA-21036:
---------------------------------------------

CI results to follow

> Better support for CMS initialization when DOWN nodes have not been upgraded
> ----------------------------------------------------------------------------
>
>                 Key: CASSANDRA-21036
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-21036
>             Project: Apache Cassandra
>          Issue Type: Improvement
>          Components: Transactional Cluster Metadata
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>            Priority: Normal
>             Fix For: 6.x
>
>
> The {{nodetool cms initialize}} command allows the operator to supply a list of nodes to ignore when checking for consensus on the initial state of cluster metadata. If the ignored nodes have been upgraded and have begun startup prior to this point, then the rest of the cluster will view them as upgraded and everything proceeds as expected. However, if an ignored node has been DOWN for the entirety of the upgrade, peers still consider the cluster to be in a mixed state. This has an effect on the metadata serialization version that is selected as well as on which metadata transformations are permitted. It must be possible for the participating nodes to commit both the {{PreInitialize}} and {{Initialize}} transformations in order for the CMS initialization to complete.



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