You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Edward Sargisson (JIRA)" <ji...@apache.org> on 2013/04/15 19:10:16 UTC
[jira] [Commented] (FLUME-2002) Flume RPC Client creates 2 threads
per each log attempt if the remote flume agent goes down
[ https://issues.apache.org/jira/browse/FLUME-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13631876#comment-13631876 ]
Edward Sargisson commented on FLUME-2002:
-----------------------------------------
Raised from a defect originally raised in the Apache log4j2 project.
Ralph Goers in log4j2 projects says,
"I have modified FlumeAvroManager to use the Flume RPCClient. Even when using that this behavior still occurs. Once I commit the changes I will be closing this issue as it doesn't seem to be an error in the FlumeAppender but in Flume itself. It looks like NettyAvroRpcClient may not be shutting down the threads properly. "
> 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