[YARN-304] RM Tracking Links for purged applications needs a long-term solution

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 0.23.5, 3.0.0-alpha1
• Assignee: Mayank Bansal
• Reporter: Derek Dagit
• Created: 02/Jan/13 15:43
• Updated: 12/May/16 18:30
• Resolved: 01/May/15 22:01

Description

This JIRA is intended to track a proper long-term fix for the issue described in YARN-285.

The following is from the original description:

As applications complete, the RM tracks their IDs in a completed list. This list is routinely truncated to limit the total number of application remembered by the RM.

When a user clicks the History for a job, either the browser is redirected to the application's tracking link obtained from the stored application instance. But when the application has been purged from the RM, an error is displayed.

In very busy clusters the rate at which applications complete can cause applications to be purged from the RM's internal list within hours, which breaks the proxy URLs users have saved for their jobs.

We would like the RM to provide valid tracking links persist so that users are not frustrated by broken links.

Issue Links

• duplicates: YARN-321 [Umbrella] Generic application history service
• relates to: YARN-256 Increase retention of applications in AppManager without sending more applications to the UI
• relates to: MAPREDUCE-4899 Provide a plugin to the Yarn Web App Proxy to generate tracking links for M/R appllications given the ID
• relates to: YARN-285 RM should be able to provide a tracking link for apps that have already been purged
• supercedes: YARN-256 Increase retention of applications in AppManager without sending more applications to the UI