You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Thomas Graves (JIRA)" <ji...@apache.org> on 2012/09/18 18:06:07 UTC

[jira] [Created] (MAPREDUCE-4662) JobHistoryFilesManager thread pool never expands

Thomas Graves created MAPREDUCE-4662:
----------------------------------------

             Summary: 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


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