[
https://issues.apache.org/jira/browse/MAPREDUCE-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli reassigned MAPREDUCE-2961:
--------------------------------------------------
Assignee: Vinod Kumar Vavilapalli (was: Mahadev konar)
There are a couple of other bugs that need to be fixed related to
ContainerLauncher's thread pool.
- The way it is, the pool size grows to the configured core-pool-size and
stays there. We should set core-pool-size to be very low, set a max-pool-size
and bound the queue size.
- We also pre-allocate threads which affects MRAppMaster initialization time.
I am taking this up.
> Increase the default threadpool size for container launching in the
> application master.
> ---------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-2961
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2961
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Mahadev konar
> Assignee: Vinod Kumar Vavilapalli
> Priority: Blocker
> Fix For: 0.23.0
>
> Attachments: MAPREDUCE-2961.patch, MAPREDUCE-2961.patch
>
>
> Currently the default threadpool size is 10 for launching containers in
> ContainerLauncherImpl. We should increase that to 100 for a reasonable
> default, so that container launching is not backed up by a small thread pool
> size.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
