You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Sam Tunnicliffe (JIRA)" <ji...@apache.org> on 2017/02/06 15:37:41 UTC

[jira] [Updated] (CASSANDRA-13041) Do not allow removal of a DC from system_auth replication settings if the DC has active Cassandra instances

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

Sam Tunnicliffe updated CASSANDRA-13041:
----------------------------------------
    Status: Awaiting Feedback  (was: In Progress)

> 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)