[
https://issues.apache.org/jira/browse/CASSANDRA-20736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-20736:
----------------------------------------
Change Category: Semantic
Complexity: Normal
Fix Version/s: 6.0
Status: Open (was: Triage Needed)
Patch is included with CASSANDRA-20476 here:
[4613|https://github.com/apache/cassandra/pull/4613]
> Add CMS membership as a field in ClusterMetadata
> ------------------------------------------------
>
> Key: CASSANDRA-20736
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20736
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Cluster/Membership
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Normal
> Fix For: 6.0
>
>
> Rather than inferring membership of the CMS from the DataPlacement for
> keyspaces with MetaStrategy replication, the membership should be explicitly
> encoded in ClusterMetadata. That DataPlacement can then be calculated from it
> and we can ensure that it isn't able to be modified directly by
> transformations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
