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

["Zhijie Shen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/YARN-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13863297#comment-13863297 ] 

Zhijie Shen commented on YARN-304:
----------------------------------

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

With AHS is deployed, users are able to track the completed applications even when they are purged from RM in-memory store. The problem is to help users to seamlessly access the applications on AHS given they only have the proxy URLs on hand. RM needs to translate the URLs and redirect the users to AHS.

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

A related issue here is that if an application is killed/failed, or it doesn't provide an updated tracking URL when unregistering, users may not have the proxy URL to track the application after it is completed. "History" link is pointing to the app page in RM itself. It should be good to by default set the tracking URL to AHS if it is not updated when an application is to complete.

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