[
https://issues.apache.org/jira/browse/MAPREDUCE-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421232#comment-13421232
]
Hadoop QA commented on MAPREDUCE-4438:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12537655/MAPREDUCE-4438-3.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 2 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-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell
hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-unmanaged-am-launcher.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2650//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2650//console
This message is automatically generated.
> Add client side for UnmanagedRM
> -------------------------------
>
> Key: MAPREDUCE-4438
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4438
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Affects Versions: 3.0.0
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Attachments: MAPREDUCE-4438-1.patch, MAPREDUCE-4438-2.patch,
> MAPREDUCE-4438-3.patch
>
>
> MAPREDUCE-4427 added server side support for umanaged AM's. This tracks
> creating client side supporting pieces.
> The basic flow of the client is as follows
> 1) accepts a cmd line for the AM. Optional queue information etc.
> 2) negotiates an application id with the RM and submits the unmanaged AM.
> 3) waits for the AM to reach YarnApplicationState ACCEPTED
> 4) then launches the AM in a separate process via the cmd provided. It
> communicated application attempt id to the AM via env variable. Stdout and
> stderr is redirected to the clients streams respectively.
> 5) waits for the AM process to exit and RM app to complete.
--
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
