You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Daniel Templeton (JIRA)" <ji...@apache.org> on 2016/03/08 21:08:40 UTC

[jira] [Updated] (YARN-4767) Network issues can cause persistent RM UI outage

     [ https://issues.apache.org/jira/browse/YARN-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Templeton updated YARN-4767:
-----------------------------------
    Attachment: YARN-4767.001.patch

Here's a patch that resolves the issue.  The general idea is correct, but I'd love some feedback on how this patch jives with the usual web UI flow.

> 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)