[
https://issues.apache.org/jira/browse/MAPREDUCE-6362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mit Desai updated MAPREDUCE-6362:
---------------------------------
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.
With the current plugin in place, redirections for the Mapreduce jobs works but
we need the add functionality for tez jobs
was:
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.
> History Plugin should be updated
> --------------------------------
>
> Key: MAPREDUCE-6362
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6362
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 2.6.1
> Reporter: Mit Desai
> Assignee: Mit Desai
>
> 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.
> With the current plugin in place, redirections for the Mapreduce jobs works
> but we need the add functionality for tez jobs
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
