You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Ashish Paliwal (JIRA)" <ji...@apache.org> on 2013/11/19 05:55:21 UTC
[jira] [Updated] (FLUME-2238) Provide option to configure worker
threads in NettyAvroRpcClient
[ https://issues.apache.org/jira/browse/FLUME-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ashish Paliwal updated FLUME-2238:
----------------------------------
Description:
>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
was:
>From dev ML, Creadits 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
> 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
>
> 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#6144)