[
https://issues.apache.org/jira/browse/YARN-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Derek Dagit updated YARN-285:
-----------------------------
Attachment: YARN-285.patch
This is a patch that introduces handling for an optional tracking URI plugin,
specified via a new config, that should accept a given ApplicationId and return
a valid URI.
The plugin is used in cases where a proxy link is requested, but the RM has
already purged the given application. The plugin will use the ApplicationId to
rewrite the URL, and the browser will be redirected just as when the RM uses
the tracking URL of a application the it knows about.
The intention of the plugin instead of a simple URL rewrite is to keep
architectural separation between Yarn and MapReduce.
The mechanism is similar to that involving the ResourceCalculatorPlugin.
> RM should be able to provide a tracking link for apps that have already been
> purged
> -----------------------------------------------------------------------------------
>
> Key: YARN-285
> URL: https://issues.apache.org/jira/browse/YARN-285
> Project: Hadoop YARN
> Issue Type: Improvement
> Affects Versions: 3.0.0, 0.23.5
> Reporter: Derek Dagit
> Assignee: Derek Dagit
> Attachments: YARN-285-branch-0.23.patch, YARN-285.patch
>
>
> 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
