cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (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 Wed, 14 Dec 2016 11:46:58 GMT

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

Sam Tunnicliffe commented on CASSANDRA-13041:
---------------------------------------------

bq. dropping the keyspace system_auth should not be allowed

{{system_auth}} is already non-droppable, though some of the tables in it which pre-date {{2.2}}
can be removed by an operator (in fact this is the final stage of migrating auth data when
upgrading from older versions).

> 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
>
>
> 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.4#6332)

Mime
View raw message