[
https://issues.apache.org/jira/browse/YARN-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13900806#comment-13900806
]
Vinod Kumar Vavilapalli commented on YARN-304:
----------------------------------------------
Can we keep this open to track the removal of the plugin added at YARN-285 ?
> 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
(v6.1.5#6160)
