[
https://issues.apache.org/jira/browse/FLUME-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Paliwal updated FLUME-2243:
----------------------------------
Attachment: FLUME-2243-1.patch
Rebased the patch.
Removed TransreceiverThreadFactory class and used Guava ThreadNamingFactory.
Removed Unused imports
> AvroSource to use TransceiverThreadFactory for Thread naming while
> initializing NioServerSocketChannelFactory
> -------------------------------------------------------------------------------------------------------------
>
> Key: FLUME-2243
> URL: https://issues.apache.org/jira/browse/FLUME-2243
> Project: Flume
> Issue Type: Improvement
> Components: Sinks+Sources
> Affects Versions: v1.4.0
> Reporter: Ashish Paliwal
> Assignee: Ashish Paliwal
> Priority: Minor
> Attachments: FLUME-2243-0.patch, FLUME-2243-1.patch
>
>
> Currently in Avro source, we use
> socketChannelFactory = new NioServerSocketChannelFactory
> (Executors .newCachedThreadPool(), Executors.newCachedThreadPool());
> This would create generic Thread names like pool-1-thread-1. It would be good
> to use a ThreadFactory, like we use in NettyAvroRpcClient for better
> identification of Threads in log file
> ExecutorService bossExecutor = Executors.newCachedThreadPool(new
> TransceiverThreadFactory(
> "Avro " + NettyTransceiver.class.getSimpleName() + " Boss"));
> ExecutorService workerExecutor = Executors.newCachedThreadPool(new
> TransceiverThreadFactory(
> "Avro " + NettyTransceiver.class.getSimpleName() + " I/O Worker"));
> Move the TransceiverThreadFactory class to util package (from private static
> class) and update the usage in code.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
