[
https://issues.apache.org/jira/browse/FLUME-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13931062#comment-13931062
]
Hudson commented on FLUME-2243:
-------------------------------
SUCCESS: Integrated in flume-trunk #561 (See
[https://builds.apache.org/job/flume-trunk/561/])
FLUME-2243. Avro Source should name threads instead of using generic names.
(hshreedharan:
http://git-wip-us.apache.org/repos/asf/flume/repo/?p=flume.git&a=commit&h=47507bc40202c52e7156106642ffc0ab849fb96e)
* flume-ng-core/src/main/java/org/apache/flume/source/AvroSource.java
> 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.2#6252)
