[
https://issues.apache.org/jira/browse/FLUME-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13645222#comment-13645222
]
Ralph Goers edited comment on FLUME-2002 at 4/30/13 4:07 AM:
-------------------------------------------------------------
It looks to me like the connect method in NettyAvroRpcClient is creating a
couple of thread pools before trying to open the connection. If a connection is
thrown it doesn't clean them up.
Also, this error also occurs if the Flume agents are not available when the
application is started.
was (Author: [email protected]):
It looks to me like the connect method in NettyAvroRpcClient is creating a
couple of thread pools before trying to open the connection. If a connection is
thrown it doesn't clean them up.
> Flume RPC Client creates 2 threads per each log attempt if the remote flume
> agent goes down
> -------------------------------------------------------------------------------------------
>
> Key: FLUME-2002
> URL: https://issues.apache.org/jira/browse/FLUME-2002
> Project: Flume
> Issue Type: Bug
> Components: Client SDK
> Affects Versions: v1.3.0
> Reporter: Edward Sargisson
> Attachments: Screenshot.png, zzzzzzzzzzzzzzzzzTest.tar.gz
>
>
> Steps to reproduce (use attached Maven project):
> 1. Start your remote flume agent
> 2. Run the Maven project and attach to it with the debugger in your favourite
> IDE (I use NetBeans)
> 3. Kill your remote flume agent
> 4. Rapidly press enter
> Each time you press Enter, 2 new threads show up. See the attached
> screenshot. Notice the panel on the left is littered with new threads. I was
> pressing Enter rapidly for 30 seconds.
> NOTE: This also happens if the remote flume agent hasn't been started at all.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
