cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11854) Remove finished streaming connections from MessagingService
Date Mon, 27 Jun 2016 07:34:52 GMT


Marcus Eriksson commented on CASSANDRA-11854:

In {{SocketThread#close()}} we iterate over the {{connections}} and close each one, this will
not work now since the {{connections}} will be empty, right? Should we perhaps {{close()}}
the socket when we remove it from {{group}}? They were only closed on server shutdown before
so maybe we don't need to do that?

> Remove finished streaming connections from MessagingService
> -----------------------------------------------------------
>                 Key: CASSANDRA-11854
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Paulo Motta
>            Assignee: Paulo Motta
>         Attachments: oom.png
> When a new {{IncomingStreamingConnection}} is created, [we register it in the connections
of {{MessagingService}}, but we [only remove it if there is an exception|]
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

View raw message