Return-Path: X-Original-To: apmail-hadoop-mapreduce-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4EA7AD1DD for ; Tue, 18 Sep 2012 16:06:09 +0000 (UTC) Received: (qmail 19252 invoked by uid 500); 18 Sep 2012 16:06:08 -0000 Delivered-To: apmail-hadoop-mapreduce-dev-archive@hadoop.apache.org Received: (qmail 18852 invoked by uid 500); 18 Sep 2012 16:06:07 -0000 Mailing-List: contact mapreduce-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-dev@hadoop.apache.org Delivered-To: mailing list mapreduce-dev@hadoop.apache.org Received: (qmail 18575 invoked by uid 99); 18 Sep 2012 16:06:07 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Sep 2012 16:06:07 +0000 Date: Wed, 19 Sep 2012 03:06:07 +1100 (NCT) From: "Thomas Graves (JIRA)" To: mapreduce-dev@hadoop.apache.org Message-ID: <1815789678.92804.1347984367509.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (MAPREDUCE-4662) JobHistoryFilesManager thread pool never expands MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 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()); } 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