You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "C. Scott Andreas (JIRA)" <ji...@apache.org> on 2018/11/19 02:33:01 UTC

[jira] [Updated] (CASSANDRA-11610) Revisit consistent range movement restrictions

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

C. Scott Andreas updated CASSANDRA-11610:
-----------------------------------------
    Component/s: Distributed Metadata

> Revisit consistent range movement restrictions
> ----------------------------------------------
>
>                 Key: CASSANDRA-11610
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11610
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Distributed Metadata
>            Reporter: Brandon Williams
>            Priority: Major
>
> I have a suspicion that we chose the wrong default by always having this on, with a flag to disable.  We ran for a very long time without it, and at most a handful of people cared, with very few complaints.  Now that we have this on, the majority who didn't care before but want to double even fairly small clusters now have to add a flag to disable it, and then are curious why they need to.
> Regardless of that, I think we need to at least make the restriction more lax; we currently block the simultaneous addition of nodes across the entire cluster, even they use NTS and have many DCs with different RF settings.  We should at least allow simultaneous addition in multiple DCs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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