[
https://issues.apache.org/jira/browse/MAPREDUCE-4662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459901#comment-13459901
]
Hadoop QA commented on MAPREDUCE-4662:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12545957/mapreduce-4662.branch-1.patch
against trunk revision .
-1 patch. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2864//console
This message is automatically generated.
> JobHistoryFilesManager thread pool never expands
> ------------------------------------------------
>
> Key: MAPREDUCE-4662
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4662
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver
> Affects Versions: 1.0.2
> Reporter: Thomas Graves
> Assignee: Kihwal Lee
> Attachments: mapreduce-4662.branch-1.patch
>
>
> The job history file manager creates a threadpool with core size 1 thread,
> max pool size 3. It never goes beyond 1 thread though because its using a
> LinkedBlockingQueue which doesn't have a max size.
> void start() {
> executor = new ThreadPoolExecutor(1, 3, 1,
> TimeUnit.HOURS, new LinkedBlockingQueue<Runnable>());
> }
> According to the ThreadPoolExecutor java doc page it only increases the
> number of threads when the queue is full. Since the queue we are using has no
> max size it never fills up and we never get more then 1 thread.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
