[
https://issues.apache.org/jira/browse/YARN-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bikas Saha moved MAPREDUCE-4427 to YARN-420:
--------------------------------------------
Fix Version/s: (was: 2.0.2-alpha)
2.0.2-alpha
Affects Version/s: (was: 3.0.0)
3.0.0
Key: YARN-420 (was: MAPREDUCE-4427)
Project: Hadoop YARN (was: Hadoop Map/Reduce)
> Enable the RM to work with AM's that are not managed by it
> ----------------------------------------------------------
>
> Key: YARN-420
> URL: https://issues.apache.org/jira/browse/YARN-420
> Project: Hadoop YARN
> Issue Type: Improvement
> Affects Versions: 3.0.0
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Labels: mrv2
> Fix For: 2.0.2-alpha
>
> Attachments: MAPREDUCE-4427-1.patch, MAPREDUCE-4427-2.patch,
> MAPREDUCE-4427-3.patch
>
>
> Currently, the RM itself manages the AM by allocating a container for it and
> negotiating the launch on the NodeManager and manages the AM lifecycle.
> Thereafter, the AM negotiates resources with the RM and launches tasks to do
> the real work.
> It would be a useful improvement to enhance this model by allowing the AM to
> be launched independently by the client without requiring the RM. These AM's
> would be launched on a gateway machine that can talk to the cluster. This
> would open up new use cases such as the following
> 1) Easy debugging of AM, specially during initial development. Having the AM
> launched on an arbitrary cluster node makes it hard to looks at logs or
> attach a debugger to the AM. If it can be launched locally then these tasks
> would be easier.
> 2) Running AM's that need special privileges that may not be available on
> machines managed by the NodeManager
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
