[
https://issues.apache.org/jira/browse/MAPREDUCE-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410984#comment-13410984
]
Hadoop QA commented on MAPREDUCE-4427:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12535920/MAPREDUCE-4427-1.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 4 new or modified test
files.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient
hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-api
hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common
hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager
hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2569//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2569//console
This message is automatically generated.
> 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
>
>
> 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