[
https://issues.apache.org/jira/browse/CASSANDRA-20801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuqi Yan updated CASSANDRA-20801:
---------------------------------
Change Category: Operability
Complexity: Low Hanging Fruit
Component/s: Consistency/Bootstrap and Decommission
Status: Open (was: Triage Needed)
> Option to schedule Paxos cleanup on topology change by keyspace
> ---------------------------------------------------------------
>
> Key: CASSANDRA-20801
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20801
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Consistency/Bootstrap and Decommission
> Reporter: Yuqi Yan
> Assignee: Yuqi Yan
> Priority: Normal
>
> We should have some configurable rate limiting within
> `repairPaxosForTopologyChange`. Currently it's starting all the
> PaxosCleanupSessions in one go.
> ([https://github.com/apache/cassandra/blob/6fd1194578ca3149ce9cd9f14a8591df71c20753/src/java/org/apache/cassandra/service/ActiveRepairService.java#L1157)]
> Number of sessions created is related to (vnodes * node_count * tables) so
> this can go really heavy.
> Looking in the log I found something like:
> {code:java}
> /x.x.x.x:xxxx->/x.x.x.x:xxxx-SMALL_MESSAGES-a9be1f48 overloaded; dropping
> 0.073KiB message (queue: 132.000MiB local, 128.000MiB endpoint, 198.713MiB
> global){code}
> the messages were most likely from the PAXOS2_CLEANUP_REQ
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
