cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nachiket Patil (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13041) Do not allow removal of a DC from system_auth replication settings if the DC has active Cassandra instances
Date Mon, 06 Feb 2017 21:11:41 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-13041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15854739#comment-15854739
] 

Nachiket Patil commented on CASSANDRA-13041:
--------------------------------------------

Thanks [~beobal] for the explanation. In this case I dont mind removing the drop-keyspace
changes. I dont see any problem with the changes you have made either. 

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

Mime
View raw message