[
https://issues.apache.org/jira/browse/YARN-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943850#comment-13943850
]
Hadoop QA commented on YARN-1577:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12636164/YARN-1577.4.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-unmanaged-am-launcher
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/3436//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3436//console
This message is automatically generated.
> Unmanaged AM is broken because of YARN-1493
> -------------------------------------------
>
> Key: YARN-1577
> URL: https://issues.apache.org/jira/browse/YARN-1577
> Project: Hadoop YARN
> Issue Type: Sub-task
> Affects Versions: 2.3.0
> Reporter: Jian He
> Assignee: Jian He
> Priority: Blocker
> Attachments: YARN-1577.1.patch, YARN-1577.2.patch, YARN-1577.3.patch,
> YARN-1577.4.patch
>
>
> Today unmanaged AM client is waiting for app state to be Accepted to launch
> the AM. This is broken since we changed in YARN-1493 to start the attempt
> after the application is Accepted. We may need to introduce an attempt state
> report that client can rely on to query the attempt state and choose to
> launch the unmanaged AM.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
