You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2014/05/14 23:19:35 UTC
[jira] [Resolved] (YARN-373) Allow an AM to reuse the resources
allocated to container for a new container
[ https://issues.apache.org/jira/browse/YARN-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alejandro Abdelnur resolved YARN-373.
-------------------------------------
Resolution: Won't Fix
[doing self-clean up of JIRAs]
> Allow an AM to reuse the resources allocated to container for a new container
> -----------------------------------------------------------------------------
>
> Key: YARN-373
> URL: https://issues.apache.org/jira/browse/YARN-373
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
> Affects Versions: 2.0.3-alpha
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
>
> When a container completes, instead the corresponding resources being freed up, it should be possible for the AM to reuse the assigned resources for a new container.
> As part of the reallocation, the AM would notify the RM about partial resources being freed up and the RM would make the necessary corrections in the corresponding node.
> With this functionality, an AM can ensure it gets a container in the same node where previous containers run.
> This will allow getting rid of the ShuffleHandler as a service in the NMs and run it as regular container task of the corresponding AM. In this case, the reallocation would reduce the CPU/MEM obtained for the original container to the what is needed for serving the shuffle. Note that in this example the MR AM would only do this reallocation for one of the many tasks that may have run in a particular node (as a single shuffle task could serve all the map outputs from all map tasks run in that node).
--
This message was sent by Atlassian JIRA
(v6.2#6252)