[ https://issues.apache.org/jira/browse/MAPREDUCE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361601#comment-14361601 ]
Tsuyoshi Ozawa commented on MAPREDUCE-6265: ------------------------------------------- [~zxu] should we also update the following line(name of property name itself)? {code} + public static final String MR_AM_CONTAINERLAUNCHER_THREADPOOL_INITIAL_SIZE = + MR_AM_PREFIX+"containerlauncher.thread-initial-size"; {code} > 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, MAPREDUCE-6265.001.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)