[
https://issues.apache.org/jira/browse/TEZ-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohini Palaniswamy updated TEZ-2018:
------------------------------------
Summary: Job Tracking and History URL should point to the Tez UI (was: Job
Tracking URL should point to the Tez UI)
This is what @Jason Lowe told me when I asked about setting tracking URL and
how it is done with JHS now.
"there's a couple of ways we do this. We have the AM set the tracking URL when
the app leaves (this is easy to do from the Tez AM side, assuming it knows how
to build the URI for the UI server). however when the app has expired from the
RM cache then the tracking URL is no longer available. So we use a plugin to
handle unknown apps. We currently only have one plugin configured and that's
for the JHS. I believe it blindly says it can handle it and sends users to the
JHS we may have to make it a bit smarter so it checks the JHS before
redirecting or make sure the tez one does the same and is configured first in
the chain"
This patch seems to be setting the tracking url (AM web service url) and
history URL (ATS url) from the Tez AM. Should I create a separate JIRA for
creating a RM plugin that will handle TEZ applications after the job is gone
from the Tez memory?
> 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.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)
