[
https://issues.apache.org/jira/browse/YARN-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13780895#comment-13780895
]
Hudson commented on YARN-1246:
------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #4493 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/4493/])
YARN-1246. Added application finish-status to ApplicationSummary for the sake
of testing given ApplicationHistoryServer is not yet ready. Contributed by
Arpit Gupta. (vinodkv:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1527205)
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/RMAppManager.java
> 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
> Fix For: 2.1.2-beta
>
> 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
