[
https://issues.apache.org/jira/browse/YARN-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187173#comment-15187173
]
Daniel Templeton commented on YARN-4767:
----------------------------------------
[~wilfreds], no that won't solve the issue. The problem is that it's not a
circular redirect. A circular redirect is A->A->A... This is a loop of: A
contacts B and is redirected to A. From the {{HttpClient}}'s perspective,
there's nothing wonky going on here.
> 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)
