You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/06/30 15:46:00 UTC
[jira] [Commented] (AVRO-3165) [avro-ipc-netty] NioEventLoopGroup
leak in NettyTransceiver
[ https://issues.apache.org/jira/browse/AVRO-3165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17372083#comment-17372083 ]
ASF subversion and git services commented on AVRO-3165:
-------------------------------------------------------
Commit 72b3c51512752f471392e3e5eaa40f954a99b752 in avro's branch refs/heads/master from Benjamin Leber
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=72b3c51 ]
AVRO-3165: Fix NettyTransceiver workerGroup leak (#1274)
> [avro-ipc-netty] NioEventLoopGroup leak in NettyTransceiver
> -----------------------------------------------------------
>
> Key: AVRO-3165
> URL: https://issues.apache.org/jira/browse/AVRO-3165
> Project: Apache Avro
> Issue Type: Bug
> Components: java
> Affects Versions: 1.10.0, 1.10.1, 1.10.2
> Reporter: Benjamin Leber
> Assignee: Benjamin Leber
> Priority: Major
> Labels: ipc, netty
> Fix For: 1.11.0
>
> Attachments: image-2021-06-30-07-53-20-767.png
>
>
> The NettyTransceiver is used on server and client side. While it requires a worker group on client side this is not necessary on server side.
> But as the worker group is initialized during the variable declaration. It is also created on the server for every new connection, but it gets never closed. This causes high off heap memory and always increasing open file descriptors.
> !image-2021-06-30-07-53-20-767.png!
> Moving the creation of the workger group into the constructor which is called on client side, solves the problem (deployed after the second 12:00 in above graph)
> I will provide a pr to fix.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)