[ 
https://issues.apache.org/jira/browse/CASSANDRA-16446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17289861#comment-17289861
 ] 

Andres de la Peña commented on CASSANDRA-16446:
-----------------------------------------------

Great, I'm running a final CI round 
[here|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/398/pipeline]
 after the rebase just in case, I can commit once it finishes.

> Parent repair sessions leak may lead to node long pauses
> --------------------------------------------------------
>
>                 Key: CASSANDRA-16446
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16446
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Consistency/Repair
>            Reporter: Berenguer Blasi
>            Assignee: Berenguer Blasi
>            Priority: Normal
>             Fix For: 4.0, 4.0-beta
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> {{ActiveRepairService}} keeps  a map `parentRepairSessions`. If these 
> sessions leak, that map can grow to a size when a node restarts 
> {{ActiveRepairService.onRestart()}} triggers a cleanup of sessions that can 
> pause nodes in a cluster for a long time.
> The proposed solution is for repairs to cleanup these sessions on all nodes 
> on completion by sending a CLEANUP message to involved nodes. Tests rely on a 
> new {{parentRepairSessionsCount()}} method on the parent repair sessions 
> MBean to keep track of these.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to