[
https://issues.apache.org/jira/browse/MAPREDUCE-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193907#comment-13193907
]
Robert Joseph Evans commented on MAPREDUCE-3706:
------------------------------------------------
Oh, I think I know now. If the application reports its state as finished the
proxy will not try to be a proxy for the request, it will instead redirect the
request to the URI provided by the AM, but if the AM has reported that it is
finished, but has not updated the URI, (just speculating here, I need to check
the code to be sure) because the jhist file is not finished being written yet,
then the AM will redirect back to the proxy, and the proxy will redirect to the
AM again. I need to confirm this and look at what we need to do to really fix
this.
> HTTP Circular redirect error on the job attempts page
> -----------------------------------------------------
>
> Key: MAPREDUCE-3706
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3706
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Thomas Graves
> Assignee: Robert Joseph Evans
> Priority: Critical
>
> submitted job and tried to go to following url:
> http://rmhost.domain.com:8088/proxy/application_1326992308313_0004/mapreduce/attempts/job_1326992308313_4_4/m/NEW
> This resulted in the following HTTP ERROR:
> HTTP ERROR 500
> Problem accessing
> /proxy/application_1326992308313_0004/mapreduce/attempts/job_1326992308313_4_4/m/NEW.
> Reason:
> Circular redirect to
> 'http://amhost.domain.com:44869/mapreduce/attempts/job_1326992308313_4_4/m/NEW'
> Caused by:
> org.apache.commons.httpclient.CircularRedirectException: Circular redirect to
> 'http://amhost.domain.com:44869/mapreduce/attempts/job_1326992308313_4_4/m/NEW'
> at
> org.apache.commons.httpclient.HttpMethodDirector.processRedirectResponse(HttpMethodDirector.java:638)
> at
> org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:179)
> at
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
> at
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
> at
> org.apache.hadoop.yarn.server.webproxy.WebAppProxyServlet.proxyLink(WebAppProxyServlet.java:148)
> at
> org.apache.hadoop.yarn.server.webproxy.WebAppProxyServlet.doGet(WebAppProxyServlet.java:269)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1221)
> at
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:66)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:900)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:834)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:795)
> Note that if you first go to the proxy at:
> http://rmhost.domain.com:8088/proxy/application_1326992308313_0004/ and then
> click the links to get here you don't get the error.
--
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
