[
https://issues.apache.org/jira/browse/YARN-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe updated YARN-227:
----------------------------
Attachment: YARN-227.patch
Patch to add diagnostics to the expired attempt indicating it timed out. Also
changed the tracking URL to point to the RM's app page when the attempt expires
so it's not left dangling, referencing an app attempt that is no longer there.
> 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
> Attachments: 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
