[
https://issues.apache.org/jira/browse/CASSANDRA-15097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Zhuang updated CASSANDRA-15097:
-----------------------------------
Test and Documentation Plan: Unittest is passed. And the code is committed
and running in Instagram production environment.
Status: Patch Available (was: Open)
> 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
>
> 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.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
