[ 
https://issues.apache.org/jira/browse/CASSANDRA-19705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcus Eriksson updated CASSANDRA-19705:
----------------------------------------
          Fix Version/s: 5.1-alpha1
                             (was: 5.x)
    Source Control Link: 
https://github.com/apache/cassandra/commit/cbe07fd57e3d94a1f2512fced3f38e69ad4b3eb2
             Resolution: Fixed
                 Status: Resolved  (was: Ready to Commit)

committed, thanks!

> Reconfigure CMS after move/bootstrap/replacement
> ------------------------------------------------
>
>                 Key: CASSANDRA-19705
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19705
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Cluster/Membership
>            Reporter: Marcus Eriksson
>            Assignee: Marcus Eriksson
>            Priority: Normal
>             Fix For: 5.1-alpha1
>
>         Attachments: ci_summary-1.html, ci_summary.html
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to