You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Derek Dagit (JIRA)" <ji...@apache.org> on 2013/01/02 16:44:12 UTC

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

Derek Dagit created YARN-304:
--------------------------------

             Summary: RM Tracking Links for purged applications needs a long-term solution
                 Key: YARN-304
                 URL: https://issues.apache.org/jira/browse/YARN-304
             Project: Hadoop YARN
          Issue Type: Improvement
    Affects Versions: 0.23.5, 3.0.0
            Reporter: Derek Dagit


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.

--
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