You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (Jira)" <ji...@apache.org> on 2021/02/10 23:34:00 UTC
[jira] [Issue Comment Deleted] (CASSANDRA-16422) Unable to ALTER
KEYSPACE while decommissioned/assassinated nodes are in gossip
[ https://issues.apache.org/jira/browse/CASSANDRA-16422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams updated CASSANDRA-16422:
-----------------------------------------
Comment: was deleted
(was: Sorry, I actually meant I would put it inside of Gossiper.java, next to DEAD_STATES, since both are defining a subset of states.)
> Unable to ALTER KEYSPACE while decommissioned/assassinated nodes are in gossip
> ------------------------------------------------------------------------------
>
> Key: CASSANDRA-16422
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16422
> Project: Cassandra
> Issue Type: Improvement
> Components: Consistency/Bootstrap and Decommission
> Reporter: Jon Meredith
> Assignee: Jon Meredith
> Priority: Normal
> Fix For: 4.0-beta
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> As part of Transient Replication added in CASSANDRA-14404, {{ALTER KEYSPACE}} had a validation check added to verify no range movement was taking place.
> The check requires all nodes to be in {{NORMAL}} state. When a node is decommissioned or assassinated then it will remain in gossip for 3 days in {{LEFT}} state (by default), preventing any keyspace alteration until it has expired from gossip, even though it is safe to make the change.
> The validation condition should be changed to all nodes being in {{NORMAL}} or {{LEFT}} state instead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org