[
https://issues.apache.org/jira/browse/CASSANDRA-19686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jon Haddad updated CASSANDRA-19686:
-----------------------------------
Summary: ALTER KEYSPACE should cleanup available_ranges_v2 when removing a
DC (was: ALTER should cleanup available_ranges_v2 when removing a DC)
> ALTER KEYSPACE should cleanup available_ranges_v2 when removing a DC
> --------------------------------------------------------------------
>
> Key: CASSANDRA-19686
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19686
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jon Haddad
> Priority: Normal
>
> The scenario:
> New DC is added
> Data is replicated to new DC for keyspace "mykeyspace" via a rebuild
> DC is dropped in replication
> DC is re-added to "mykeyspace"
> When this happens, the user is unable to rebuild as available_ranges_v2
> thinks it's unnecessary.
> We should remove mykeyspace from system.available_ranges_v2 when removing a
> DC.
> Found in 4.1
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
