[CASSANDRA-10231] Null status entries on nodes that crash during decommission of a different node

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0.0 rc2
• Component/s: Feature/Materialized Views, Legacy/Distributed Metadata
• Severity: Normal
• Assignee: Joel Knighton Assign to me
• Reporter: Joel Knighton

Authors

Joel Knighton

Reviewers

Stefania Alborghetti

• Tester: Joel Knighton
• Created: 31/Aug/15 15:28
• Updated: 16/Apr/19 09:30
• Resolved: 12/Oct/15 06:29

Description

This issue is reproducible through a Jepsen test of materialized views that crashes and decommissions nodes throughout the test.

In a 5 node cluster, if a node crashes at a certain point (unknown) during the decommission of a different node, it may start with a null entry for the decommissioned node like so:
DN 10.0.0.5 ? 256 ? null rack1

This entry does not get updated/cleared by gossip. This entry is removed upon a restart of the affected node.

This issue is further detailed in ticket 10068.

Issue Links

• is related to: CASSANDRA-10737 TestTopology.crash_during_decommission_test dtest sometimes fails due to interrupted streaming
• links to: 10231-3.0 patch
• links to: dtest