[
https://issues.apache.org/jira/browse/TEZ-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14589767#comment-14589767
]
Bing Jiang commented on TEZ-2018:
---------------------------------
{quote}
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.
{quote}
hi, [~jlowe]. Will Application History Server continue to hold the application
info if RM cache retires the application?
> App 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
> Components: UI
> Reporter: Rohini Palaniswamy
> Assignee: Prakash Ramachandran
> Priority: Critical
> Fix For: 0.6.1
>
> Attachments: TEZ-2018.1.patch, TEZ-2018.2.patch, TEZ-2018.3.patch,
> TEZ-2018.4.patch, TEZ-2018.5.patch, TEZ-2018.6.branch-0.6.patch,
> TEZ-2018.6.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)
