[
https://issues.apache.org/jira/browse/CASSANDRA-13041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898527#comment-15898527
]
Nachiket Patil commented on CASSANDRA-13041:
--------------------------------------------
[~jjirsa] Yes. In a way the change I am proposing is opposite of
CASSANDRA-12510. CASSANDRA-12510 still has a way to force decommission an
instance if it is violating the RF. `system.auth` is a special case. This patch
prevents dropping a DC from replication factor when there are enough hosts to
satisfy the RF or less than RF in that DC.
> Do not allow removal of a DC from system_auth replication settings if the DC
> has active Cassandra instances
> -----------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-13041
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13041
> Project: Cassandra
> Issue Type: Improvement
> Components: Distributed Metadata
> Reporter: Nachiket Patil
> Assignee: Nachiket Patil
> Priority: Minor
> Fix For: 4.x
>
> Attachments: trunk.diff
>
>
> I don’t believe it is ever correct to remove a DC from the system_auth
> replication settings while there are nodes up in that DC. Cassandra should
> not allow this change if there are hosts which are currently members of the
> cluster in that DC, as any request which is routed to these hosts will meet
> an unavailable. Also dropping the keyspace system_auth should not be allowed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
