[
https://issues.apache.org/jira/browse/YARN-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186126#comment-15186126
]
Wilfred Spiegelenburg commented on YARN-4767:
---------------------------------------------
In the current proxy code we have an override set that allows circular
redirects.
By default the jetty service has: http.protocol.allow-circular-redirects set to
false and we override it to true to allow some failure cases to redirect. This
was done in MAPREDUCE-3706. The real cause of the circular redirect was fixed
in MAPREDUCE-3930.
If we remove the change for the circular redirect again would that not fix this
issue and show a error?
> Network issues can cause persistent RM UI outage
> ------------------------------------------------
>
> Key: YARN-4767
> URL: https://issues.apache.org/jira/browse/YARN-4767
> Project: Hadoop YARN
> Issue Type: Bug
> Components: webapp
> Affects Versions: 2.9.0
> Reporter: Daniel Templeton
> Assignee: Daniel Templeton
> Priority: Critical
> Attachments: YARN-4767.001.patch
>
>
> If a network issue causes an AM web app to resolve the RM proxy's address to
> something other than what's listed in the allowed proxies list, the
> AmIpFilter will 302 redirect the RM proxy's request back to the RM proxy.
> The RM proxy will then consume all available handler threads connecting to
> itself over and over, resulting in an outage of the web UI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
