hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-2961) Increase the default threadpool size for container launching in the application master.
Date Fri, 23 Sep 2011 05:58:26 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vinod Kumar Vavilapalli updated MAPREDUCE-2961:
-----------------------------------------------

    Status: Open  (was: Patch Available)

Forgot about this one.

It is easy to set the number of threads dynamically. We just need to set it equal to the number
of nodes in the system. We are looking at a scalability of 10,000 nodes, so I'd put a cap
of 2000 threads, hardcoded.

> 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: Mahadev konar
>            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

        

Mime
View raw message