[
https://issues.apache.org/jira/browse/CASSANDRA-20606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hieu Ngo updated CASSANDRA-20606:
---------------------------------
Resolution: Invalid
Status: Resolved (was: Triage Needed)
> Gossip thread slows down when forceBlockingFlush is called on system.peers
> and system.peers_v2 tables
> -----------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-20606
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20606
> Project: Apache Cassandra
> Issue Type: Improvement
> Reporter: Hieu Ngo
> Assignee: Jason Brown
> Priority: Low
>
> When using batch commit log mode, the Gossip thread slows down when peers
> after a node bounces. This is because we perform a bunch of updates to the
> peers table via {{SystemKeyspace.updatePeerInfo}}, which is a synchronized
> method. How quickly each one of those individual updates takes depends on how
> busy the system is at the time wrt write traffic. If the system is largely
> quiescent, each update will be relatively quick (just waiting for the fsync).
> If the system is getting a lot of writes, and depending on the
> commitlog_sync_batch_window_in_ms, each of the Gossip thread's updates can
> get stuck in the backlog, which causes the Gossip thread to stop processing.
> We have observed in large clusters that a rolling restart causes triggers and
> exacerbates this behavior.
--
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
