[
https://issues.apache.org/jira/browse/YARN-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14313178#comment-14313178
]
Zhijie Shen commented on YARN-2246:
-----------------------------------
[~jlowe], I think we're on the same page about what's reason of duplicate
section of the tracking url.
bq. RMAppAttemptImpl is the one tacking on the extra, redundant portion based
on the path the AM unregistered.
Are you suggesting no matter how many sections after authority in the track url
like {{http(s)://tracking authority/S1/Sk/.../Sk}}, we always generates the
proxy url like {{http(s)://proxy authority/proxy/<appId>}}?
Do you suggest that we should use the original tracking url directly instead of
proxy url on the web UI? I think this should work and we may simply change the
code in RMAppAttemptImpl#generateProxyUriWithScheme:
{code}
URI result = ProxyUriUtils.getProxyUri(null, proxyUri,
applicationAttemptId.getApplicationId());
{code}
bq. I believe it will be translated properly, as it works today
Maybe I was not clear before. I didn't meant MR AM UI will not work, but
seamless view between the AM UI and history UI is not possible nowadays. For
example, I'm at
{{http://zshens-macbook-pro.local:8088/proxy/application_1423523667600_0001/mapreduce/task/task_1423523667600_0001_m_000000}}
when the app is running. After the app is completed, I refresh the page and am
redirected to
{{http://10.22.2.92:19888/jobhistory/job/job_1423523667600_0001/mapreduce/task/task_1423523667600_0001_m_000000}}.
It's no longer the mapper page but the app summary page, because
{{mapreduce/task/task_1423523667600_0001_m_000000}} are useless sections in JHS.
Think it out loudly. In general, seamless view will still be difficult with the
aforementioned solution between two tracking URLs. For example, tracking URL is
{{http://t1:p1/a/b}} first, and I'm visiting the path at
{{http://t1:p1/a/b/x/y/z}}. When the tracking URL becomes
{{http://t2:p2/c/d/e}}, I refresh the package and am redirected
{{http://t2:p2/c/d/e/a/b/x/y/z}}. Without mapping between original tracking url
and proxy url, we don't know */a/b* is part of tracking url base, and it
shouldn't be carried on.
> Job History Link in RM UI is redirecting to the URL which contains Job Id
> twice
> -------------------------------------------------------------------------------
>
> Key: YARN-2246
> URL: https://issues.apache.org/jira/browse/YARN-2246
> Project: Hadoop YARN
> Issue Type: Bug
> Components: webapp
> Reporter: Devaraj K
> Assignee: Devaraj K
> Fix For: 2.7.0
>
> Attachments: MAPREDUCE-4064-1.patch, MAPREDUCE-4064.patch,
> YARN-2246.patch
>
>
> {code:xml}
> http://xx.x.x.x:19888/jobhistory/job/job_1332435449546_0001/jobhistory/job/job_1332435449546_0001
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
