[ https://issues.apache.org/jira/browse/YARN-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13592823#comment-13592823 ]
Jonathan Eagles commented on YARN-227: -------------------------------------- It looks like the eclipse:eclipse issue is spurious. > Application expiration difficult to debug for end-users > ------------------------------------------------------- > > Key: YARN-227 > URL: https://issues.apache.org/jira/browse/YARN-227 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager > Affects Versions: 0.23.3, 2.0.1-alpha > Reporter: Jason Lowe > Assignee: Jason Lowe > Labels: usability > Attachments: YARN-227-branch-0.23.patch, YARN-227.patch > > > When an AM attempt expires the AMLivelinessMonitor in the RM will kill the > job and mark it as failed. However there are no diagnostic messages set for > the application indicating that the application failed because of expiration. > Even if the AM logs are examined, it's often not obvious that the > application was externally killed. The only evidence of what happened to the > application is currently in the RM logs, and those are often not accessible > by users. -- 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