[CASSANDRA-17776] When doing a host replacement, -Dcassandra.broadcast_interval_ms is used to know when to check the ring but checks that the ring wasn't changed in -Dcassandra.ring_delay_ms, changes to ring delay should not depend on when we publish load stats

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 5.0-alpha1, 5.0
• Component/s: Consistency/Bootstrap and Decommission
• Bug Category: Correctness - API / Semantic Implementation
• Severity: Normal
• Complexity: Low Hanging Fruit
• Discovered By: User Report
• Platform: All
• Since Version: 3.0.0

Source Control Link

https://github.com/apache/cassandra/commit/2251c4390015853a506223534daf4046289b802e

Test and Documentation Plan

run existing tests

• Assignee: David Capwell
• Reporter: David Capwell

Authors

David Capwell

Reviewers

Brandon Williams, Caleb Rackliffe

• Created: 25/Jul/22 22:57
• Updated: 12/Sep/23 13:02
• Resolved: 26/Jul/22 20:49

Description

In some cases changing the ring delay to be higher is desired (such as when network is slower), but in order to do a host replacement operators need to know that there is a relationship with -Dcassandra.broadcast_interval_ms which is used to publish LOAD via gossip. This relationship should not be relied on and instead we should sleep based off ring delay rather than delay when we publish loads.

Issue Links

• links to: CI: trunk
• links to: GH: trunk