[jira] [Resolved] (FLUME-2244) AvroSource to use TransceiverThreadFactory for Thread naming while initializing NioServerSocketChannelFactory

["Ashish Paliwal (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLUME-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ashish Paliwal resolved FLUME-2244.
-----------------------------------

    Resolution: Duplicate

2 JIRA's got created with same content, some local issue

> AvroSource to use TransceiverThreadFactory for Thread naming while initializing NioServerSocketChannelFactory
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: FLUME-2244
>                 URL: https://issues.apache.org/jira/browse/FLUME-2244
>             Project: Flume
>          Issue Type: Improvement
>          Components: Sinks+Sources
>    Affects Versions: v1.4.0
>            Reporter: Ashish Paliwal
>            Priority: Minor
>
> 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"));



--
This message was sent by Atlassian JIRA
(v6.1#6144)