[ https://issues.apache.org/jira/browse/YARN-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15447051#comment-15447051 ]
Daniel Templeton commented on YARN-4767: ---------------------------------------- Actually, I am testing with the "cluster" prefix in {{TestWebAppProxyServet}}. In these lines: {code} String expected = WebAppUtils.getResolvedRMWebAppURLWithScheme(configuration) + "/failure/application_00_0"; {code} the {{WebAppUtils.getResolvedRMWebAppURLWithScheme(configuration)}} call adds the prefix, so the expected path is "/cluster/failure/application_00_0". > 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.7.2 > Reporter: Daniel Templeton > Assignee: Daniel Templeton > Priority: Critical > Attachments: YARN-4767.001.patch, YARN-4767.002.patch, > YARN-4767.003.patch, YARN-4767.004.patch, YARN-4767.005.patch, > YARN-4767.006.patch, YARN-4767.007.patch, YARN-4767.008.patch, > YARN-4767.009.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) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org