Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Fri, 13 Mar 2015 05:12:38 +0000 (UTC)
From: "Tsuyoshi Ozawa (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12776783.1424681219000.82971.1426223558844@Atlassian.JIRA>
In-Reply-To: <JIRA.12776783.1424681219000@Atlassian.JIRA>
References: <JIRA.12776783.1424681219000@Atlassian.JIRA>
 <JIRA.12776783.1424681219065@arcas>
Subject: [jira] [Commented] (MAPREDUCE-6265) make INITIAL_POOL_SIZE in
 ContainerLauncherImpl configurable to better control the thread pool size
 to launch/kill containers.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MAPREDUCE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359952#comment-14359952 ] 

Tsuyoshi Ozawa commented on MAPREDUCE-6265:
-------------------------------------------

Sure, I'll check it.

> make INITIAL_POOL_SIZE in ContainerLauncherImpl configurable to better control the thread pool size to launch/kill containers.
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-6265
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6265
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mrv2
>            Reporter: zhihai xu
>            Assignee: zhihai xu
>         Attachments: MAPREDUCE-6265.000.patch
>
>
> make INITIAL_POOL_SIZE in ContainerLauncherImpl configurable to better control the thread pool size to launch/kill containers
> Currently INITIAL_POOL_SIZE in ContainerLauncherImpl is hard-coded at 
> {code}
>   protected static final int INITIAL_POOL_SIZE = 10;
> {code}
> We should make it configurable because the thread pool size will be decided by INITIAL_POOL_SIZE, limitOnPoolSize and number of node used by the AM.
> Since we already made limitOnPoolSize configurable, it make senses to also make INITIAL_POOL_SIZE configurable to better manage the thread pool size.
> We saw some issue due to the small thread pool size when some node is down. The recovery from a shutdown node take very long time due to all the ContainerLauncher threads are blocked by IPC client connection to the shutdown node.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)