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

["Stefan Miklosovic (Jira)" <ji...@apache.org>]

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

Stefan Miklosovic commented on CASSANDRA-13041:
-----------------------------------------------

This was already implemented in CASSANDRA-17478. The approach taken there went without guardrail so I think that this ticket is not relevant anymore.

> 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: Legacy/Distributed Metadata
>            Reporter: Nachiket Patil
>            Assignee: Stefan Miklosovic
>            Priority: Low
>             Fix For: 5.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
(v8.20.10#820010)

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