[
https://issues.apache.org/jira/browse/TEZ-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14305247#comment-14305247
]
Jason Lowe commented on TEZ-2018:
---------------------------------
bq. Maybe this plugin could be enhanced to do the redirection based on the
application type field which YARN is aware of.
The plugin is only invoked when YARN (the RM in this case) has lost track of
the application because it expired from the cache of completed applications.
On a busy cluster this can occur rather quickly, within hours of the app
completing. Since the RM doesn't have any knowledge of the app, all it has is
the app ID from the proxy request. Therefore that's all we can send to the
tracking url plugin.
Rather than going the plugin route, a better fix would be to persist app
information (via the ATS/AHS) and have the web proxy query that when it's not
in the apps cache. The plugin route is to cover the period before that's all
worked out. It also helps cover the case where the ATS/AHS is not enabled,
since it's currently not a requirement for a YARN cluster.
> Job Tracking and History URL should point to the Tez UI
> -------------------------------------------------------
>
> Key: TEZ-2018
> URL: https://issues.apache.org/jira/browse/TEZ-2018
> Project: Apache Tez
> Issue Type: New Feature
> Reporter: Rohini Palaniswamy
> Assignee: Prakash Ramachandran
> Priority: Critical
> Attachments: TEZ-2018.1.patch, TEZ-2018.2.patch, TEZ-2018.wip.1.patch
>
>
> We need to have the Job Tracking URL take users to the Tez UI if
> yarn.timeline-service.enabled=true
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
