[YARN-227] Application expiration difficult to debug for end-users

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.23.3, 2.0.1-alpha
• Fix Version/s: 0.23.7, 2.1.0-beta
• Component/s: resourcemanager
• Labels: usability
• Target Version/s: 2.0.3-alpha, 0.23.7
• Assignee: Jason Darrell Lowe
• Reporter: Jason Darrell Lowe
• Created: 19/Nov/12 20:57
• Updated: 03/Sep/14 22:54
• Resolved: 05/Mar/13 23:33

Description

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.

Issue Links

• blocks: YARN-414 [Umbrella] Usability issues in YARN