[CASSANDRA-8252] dtests that involve topology changes should verify system.peers on all nodes

• Type: Improvement
• Status: Open
• Priority: Normal
• Resolution: Unresolved
• Fix Version/s: 2.1.x
• Component/s: Test/dtest/python
• Assignee: Ryan McGuire Assign to me
• Reporter: Brandon Williams

Authors

Ryan McGuire

• Created: 04/Nov/14 17:40
• Updated: 17/Aug/21 10:29

Description

This is especially true for replace where I've discovered it's wrong in 1.2.19, which is sad because now it's too late to fix. We've had a lot of problems with incorrect/null system.peers, so after any topology change we should verify it on every live node when everything is finished.

Issue Links

• Is contained by: CASSANDRA-9012 Triage missing test coverage
• is depended upon by: CASSANDRA-8304 Explore evicting replacement state sooner
• relates to: CASSANDRA-9180 Failed bootstrap/replace attempts persist entries in system.peers