You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Kannan Rajah (JIRA)" <ji...@apache.org> on 2014/12/04 03:40:15 UTC
[jira] [Assigned] (MAPREDUCE-3902) MR AM should reuse containers
for map tasks, there-by allowing fine-grained control on num-maps for users
without need for CombineFileInputFormat etc.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kannan Rajah reassigned MAPREDUCE-3902:
---------------------------------------
Assignee: Kannan Rajah (was: Siddharth Seth)
> MR AM should reuse containers for map tasks, there-by allowing fine-grained control on num-maps for users without need for CombineFileInputFormat etc.
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3902
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3902
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: applicationmaster, mrv2
> Reporter: Arun C Murthy
> Assignee: Kannan Rajah
> Attachments: AMContainerRefactorNotes.pdf, AM_ContainerRefactor.pdf, MAPREDUCE-3902.2.patch, MAPREDUCE-3902.patch
>
>
> The MR AM is now in a great position to reuse containers across (map) tasks. This is something similar to JVM re-use we had in 0.20.x, but in a significantly better manner:
> # Consider data-locality when re-using containers
> # Consider the new shuffle - ensure that reduces fetch output of the whole container at once (i.e. all maps) : MAPREDUCE-4525
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)