[
https://issues.apache.org/jira/browse/YARN-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13780565#comment-13780565
]
Hadoop QA commented on YARN-1246:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12605595/YARN-1246.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
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-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/2031//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2031//console
This message is automatically generated.
> Log application status in the rm log when app is done running
> -------------------------------------------------------------
>
> Key: YARN-1246
> URL: https://issues.apache.org/jira/browse/YARN-1246
> Project: Hadoop YARN
> Issue Type: Improvement
> Affects Versions: 2.1.1-beta
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Priority: Minor
> Attachments: YARN-1246.patch
>
>
> Since there is no yarn history server it becomes difficult to determine what
> the status of an old application is. One has to be familiar with the state
> transition in yarn to know what means a success.
> We should add a log at info level that captures what the finalStatus of an
> app is. This would be helpful while debugging applications if the RM has
> restarted and we no longer can use the UI.
--
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
