[YARN-337] RM handles killed application tracking URL poorly

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.2-alpha, 0.23.5
• Fix Version/s: 0.23.10, 2.1.1-beta
• Component/s: resourcemanager
• Labels: usability
• Target Version/s: 0.23.10, 2.1.1-beta
• Hadoop Flags: Reviewed
• Assignee: Jason Darrell Lowe
• Reporter: Jason Darrell Lowe
• Created: 11/Jan/13 20:44
• Updated: 03/Sep/14 23:50
• Resolved: 14/Aug/13 14:28

Description

When the ResourceManager kills an application, it leaves the proxy URL redirecting to the original tracking URL for the application even though the ApplicationMaster is no longer there to service it. It should redirect it somewhere more useful, like the RM's web page for the application, where the user can find that the application was killed and links to the AM logs.

In addition, sometimes the AM during teardown from the kill can attempt to unregister and provide an updated tracking URL, but unfortunately the RM has "forgotten" the AM due to the kill and refuses to process the unregistration. Instead it logs:

2013-01-09 17:37:49,671 [IPC Server handler 2 on 8030] ERROR
org.apache.hadoop.yarn.server.resourcemanager.ApplicationMasterService: AppAttemptId doesnt exist in cache appattempt_1357575694478_28614_000001

It should go ahead and process the unregistration to update the tracking URL since the application offered it.

Issue Links

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