[
https://issues.apache.org/jira/browse/CASSANDRA-15097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Zhuang updated CASSANDRA-15097:
-----------------------------------
Fix Version/s: 4.0
3.11.5
3.0.19
Source Control Link:
[3f70e7c72c703bc323b169a28e8754ce67d4e479|https://github.com/apache/cassandra/commit/3f70e7c72c703bc323b169a28e8754ce67d4e479]
Since Version: 3.0.0
Status: Resolved (was: Ready to Commit)
Resolution: Fixed
Thanks [~samt] for the review. Committed as
[3f70e7c|https://github.com/apache/cassandra/commit/3f70e7c72c703bc323b169a28e8754ce67d4e479].
> Avoid updating unchanged gossip state
> -------------------------------------
>
> Key: CASSANDRA-15097
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15097
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Gossip
> Reporter: Jay Zhuang
> Assignee: Jay Zhuang
> Priority: Normal
> Fix For: 3.0.19, 3.11.5, 4.0
>
>
> The node might get unchanged gossip states, the state might be just updated
> after sending a GOSSIP_SYN, then it will get the state that is already up to
> date. If the heartbeat in the GOSSIP_ACK message is updated, it will
> unnecessary re-apply the same state again, which could be costly like
> updating token change.
> It's very likely to happen for large cluster when a node startup, as the
> first gossip message will sync all endpoints tokens, it could take some time
> (in our case about 200 seconds), during that time, it keeps gossip with other
> node and get the full token states. Which causes lots of pending gossip tasks.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
