Created the JIRA https://issues.apache.org/jira/browse/FLUME-2238 and added
credits to you.Please attach the patch to it.
Solution would be to use threads as parameter to
the NioServerSocketChannelFactory constructor using it as worker count or
introduce a new variable for worker count.
I would spend some time understanding the use of Worker Executor +
On Sat, Nov 16, 2013 at 5:11 AM, Cameron Gandevia <[EMAIL PROTECTED]>wrote:
> Recently we noticed some of our embedded flume agents were using around 50
> netty IO worker threads.
> We tracked it 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.
> I can create a JIRA and a patch that allows users to configure this setting
> on the AvroSink, but I wanted to bring it up with the flume developers
> before proceeding.
My Photo Galleries: http://www.pbase.com/ashishpaliwal