You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2016/07/18 18:22:22 UTC
[jira] [Updated] (CASSANDRA-11854) Remove finished streaming
connections from MessagingService
[ https://issues.apache.org/jira/browse/CASSANDRA-11854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Yeschenko updated CASSANDRA-11854:
------------------------------------------
Fix Version/s: (was: 3.9)
3.8
> Remove finished streaming connections from MessagingService
> -----------------------------------------------------------
>
> Key: CASSANDRA-11854
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11854
> Project: Cassandra
> Issue Type: Bug
> Reporter: Paulo Motta
> Assignee: Paulo Motta
> Fix For: 2.1.15, 2.2.7, 3.0.8, 3.8
>
> Attachments: oom.png
>
>
> When a new {{IncomingStreamingConnection}} is created, [we register it in the connections map|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/net/MessagingService.java#L1109] of {{MessagingService}}, but we [only remove it if there is an exception|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/net/IncomingStreamingConnection.java#L83] while attaching the socket to the stream session.
> On nodes with SSL and large number of vnodes, after many repair sessions these old connections can accumulate and cause OOM (heap dump attached).
> The connection should be removed from the connections map after if it's finished in order to be garbage collected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)