[CASSANDRA-16422] Unable to ALTER KEYSPACE while decommissioned/assassinated nodes are in gossip

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0-rc1, 4.0
• Component/s: Consistency/Bootstrap and Decommission
• Change Category: Operability
• Complexity: Normal
• Platform: All

Source Control Link

https://github.com/apache/cassandra/commit/2d80e9904b46474b3a7cc135690c27511a234713

Test and Documentation Plan

Extended the assassinate tests to demonstrate the problem

• Assignee: Jon Meredith
• Reporter: Jon Meredith

Authors

Jon Meredith

Reviewers

Brandon Williams, David Capwell

• Created: 04/Feb/21 20:56
• Updated: 25/Feb/21 10:10
• Resolved: 12/Feb/21 17:43

Description

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.