[
https://issues.apache.org/jira/browse/YARN-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13780536#comment-13780536
]
Arpit Gupta commented on YARN-1246:
-----------------------------------
With the patch we get the following log
{code}
2013-09-27 15:57:33,168 INFO
org.apache.hadoop.yarn.server.resourcemanager.RMAppManager$ApplicationSummary:
appId=application_1380322579407_0001,name=Sleep
job,user=arpit,queue=default,state=FINISHED,trackingUrl=teamramrod.local:8088/proxy/application_1380322579407_0001/jobhistory/job/job_1380322579407_0001,appMasterHost=teamramrod.local,startTime=1380322596320,finishTime=1380322646271,finalStatus=SUCCEEDED
{code}
The following text was added to the end of the existing log
{code}
,finalStatus=SUCCEEDED
{code}
> 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
