hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Joseph Evans (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4064) Job History Link in RM UI is redirecting to the URL which contains Job Id twice
Date Tue, 27 Mar 2012 14:16:30 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239488#comment-13239488

Robert Joseph Evans commented on MAPREDUCE-4064:

Having the changes only apply when doing a redirect will fix the problem for Map Reduce, but
I think the underlying cause of the issue is not with the proxy itself.  I believe that the
proxy is working as designed, the problem is with the code that is producing the URI.

I believe that the issue is with ProxyUriUtils.getProxyUri().  It is adding on the extra path
part that should be removed.  It should always act as if the trackingUri parameter is null.
 And if that is the case that parameter should just be removed, which will simplify things
in RMAppAttemptImpl.java because we will not have to ever regenerate the proxiedTrackingUrl.

I am fairly sure that I put this bug in so thank you for finding it and trying to fix it.

> Job History Link in RM UI is redirecting to the URL which contains Job Id twice
> -------------------------------------------------------------------------------
>                 Key: MAPREDUCE-4064
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4064
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.1
>            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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message