[CASSANDRA-19705] Reconfigure CMS after move/bootstrap/replacement

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 5.1-alpha1
• Component/s: Cluster/Membership
• Epic Link: CEP-21: Follow Up
• Change Category: Semantic
• Complexity: Normal
• Platform: All

Source Control Link

https://github.com/apache/cassandra/commit/cbe07fd57e3d94a1f2512fced3f38e69ad4b3eb2

Test and Documentation Plan

New tests added

• Assignee: Marcus Eriksson
• Reporter: Marcus Eriksson

Authors

Marcus Eriksson

Reviewers

Sam Tunnicliffe

• Created: 14/Jun/24 11:33
• Updated: 04/Sep/24 16:27
• Resolved: 02/Jul/24 07:04

Description

The CMS placement uses SimpleStrategy/NTS to decide where it is placed to make it easier to safely bounce a cluster using existing tools (with CMS placement dc1: 3, dc2: 3 we will use the placements for min_token in a NetworkTopologyStrategy with the same replication setting).

We need to reconfigure this after move/bootstrap/replacement though, since the placements might have changed.

Issue Links

• is related to: CASSANDRA-19847 Create a fuzz test that randomizes topology changes, cluster actions, and CQL operations
• relates to: CASSANDRA-19794 NPE on Directory access during Memtable flush fails ShortPaxosSimulationTest
• links to: GitHub Pull Request #3375