[ 
https://issues.apache.org/jira/browse/MAPREDUCE-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414228#comment-13414228
 ] 

Bikas Saha commented on MAPREDUCE-4427:
---------------------------------------

Actually I will remove the "lfs.mkdir(containerDir, null, true)" change. It is 
unrelated to this jira. It was a workaround to an existing bug that task launch 
will fail if there are no cache items associated with it because in that case 
localization is not triggered.
                
> Enable the RM to work with AM's that are not managed by it
> ----------------------------------------------------------
>
>                 Key: MAPREDUCE-4427
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4427
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>    Affects Versions: 3.0.0
>            Reporter: Bikas Saha
>            Assignee: Bikas Saha
>              Labels: mrv2
>         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: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to