hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (YARN-304) RM Tracking Links for purged applications needs a long-term solution
Date Thu, 13 Feb 2014 18:31:21 GMT

     [ https://issues.apache.org/jira/browse/YARN-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Zhijie Shen resolved YARN-304.

    Resolution: Duplicate

Review the requirement again. It seems that the requirement has already been met by AHS. The
finished applications will be served by AHS and the tracking links are persisted if they exist.
Please feel free to reopen it if you think something is still missing.

> 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: Sub-task
>    Affects Versions: 3.0.0, 0.23.5
>            Reporter: Derek Dagit
>            Assignee: Zhijie Shen
> 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 was sent by Atlassian JIRA

View raw message