[
https://issues.apache.org/jira/browse/FLUME-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13826200#comment-13826200
]
Ashish Paliwal commented on FLUME-2238:
---------------------------------------
Would be good to add a new variable like maxIoWorkers, which if specified
initializes the appropriate NioClientSocketChannelFactory constructor.
> 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)
