[
https://issues.apache.org/jira/browse/FLUME-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844154#comment-13844154
]
Hudson commented on FLUME-2238:
-------------------------------
FAILURE: Integrated in flume-trunk #524 (See
[https://builds.apache.org/job/flume-trunk/524/])
FLUME-2238. Provide option to configure worker threads in NettyAvroRpcClient
(hshreedharan:
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=753e4137918b5bdf559dd50a21db2a832aa1dce3)
* flume-ng-doc/sphinx/FlumeUserGuide.rst
* flume-ng-sdk/src/test/java/org/apache/flume/api/TestNettyAvroRpcClient.java
* flume-ng-sdk/src/main/java/org/apache/flume/api/NettyAvroRpcClient.java
*
flume-ng-sdk/src/main/java/org/apache/flume/api/RpcClientConfigurationConstants.java
> Provide option to configure worker threads in NettyAvroRpcClient
> ----------------------------------------------------------------
>
> Key: FLUME-2238
> URL: https://issues.apache.org/jira/browse/FLUME-2238
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Affects Versions: v1.4.0
> Reporter: Ashish Paliwal
> Assignee: Cameron Gandevia
> Fix For: v1.5.0
>
> Attachments: FLUME-2238.patch
>
>
> From dev ML, Credits to Cameron Gandevia
> Embedded flume agents were using around 50 netty IO worker threads.
> The issue was tracked down to the NettyAvroRpcClient which instantiates
> the NioClientSocketChannelFactory with the default workerCount (2 * the
> number of available processors). We would like finer control over the
> number of IO threads we dedicate to flume
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
