[
https://issues.apache.org/jira/browse/YARN-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14308101#comment-14308101
]
Jason Lowe commented on YARN-2246:
----------------------------------
I think the bug is in RMAppAttemptImpl. When the AM unregisters,
RMAppAttemptImpl.generateProxyUriWithScheme will take whatever URL the AM
specified and replace the server with the proxy URL, e.g.: tracking URL
http://x/y/z becomes http://rmaddr/proxy/appid/y/z. Then when the webproxy
processes that URL it just replaces http://rmaddr/proxy/appid with the tracking
URL, leading to http://x/y/z/y/z. IMHO the proxy URL advertised to clients
should always be http://rmaddr/proxy/appid, without other stuff tacked on the
end. That can map to whatever tracking URL the app provided when processed by
the webproxy.
I also wonder if we should list the final tracking URL on the RM UI rather than
the proxy URL. Seems simpler to just direct them to the final tracking URL
rather than through the RM proxy, unless there's a use case where the client
can't reach the final tracking URL directly and needs to go through the proxy.
I haven't heard of such a setup.
> 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
> Affects Versions: 3.0.0, 0.23.11, 2.5.0
> Reporter: Devaraj K
> Assignee: Devaraj K
> Attachments: MAPREDUCE-4064-1.patch, MAPREDUCE-4064.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)
