[ https://issues.apache.org/jira/browse/CASSANDRA-17776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Capwell updated CASSANDRA-17776: -------------------------------------- Bug Category: Parent values: Correctness(12982)Level 1 values: API / Semantic Implementation(12988) Complexity: Low Hanging Fruit Discovered By: User Report Fix Version/s: 4.x Severity: Normal Assignee: David Capwell Status: Open (was: Triage Needed) > 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 > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: CASSANDRA-17776 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17776 > Project: Cassandra > Issue Type: Bug > Components: Consistency/Bootstrap and Decommission > Reporter: David Capwell > Assignee: David Capwell > Priority: Normal > Fix For: 4.x > > > 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. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org