[CASSANDRA-17883] Node will not get schema updates if it replaces a removed node with the same address

• Type: Bug
• Status: Open
• Priority: Normal
• Resolution: Unresolved
• Fix Version/s: 3.0.x, 3.11.x, 4.0.x, 5.x
• Component/s: Legacy/Distributed Metadata
• Bug Category: Correctness - Consistency
• Severity: Normal
• Complexity: Normal
• Discovered By: User Report
• Platform: All
• Assignee: Unassigned
• Reporter: Jacek Lewandowski
• Created: 12/Sep/22 09:25
• Updated: 18/Apr/23 04:15

Description

If a node is removed and then a node with the same address is added, it is ignored by migration coordinator - that is, when that node fails to push the schema change, the other nodes will not be able pull it later during periodic update.

Such situation will last until the other nodes gets restarted.

This is caused by permanently adding the address of the node being removed to the ignore list in migration coordinator.

Issue Links

• Discovered while testing: CASSANDRA-17819 Test failure: org.apache.cassandra.distributed.test.SchemaTest.schemaReset