[
https://issues.apache.org/jira/browse/YARN-10786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17350861#comment-17350861
]
Qi Zhu commented on YARN-10786:
-------------------------------
Thanks [~Song Jiacheng] for report this.
Can you add some image to confirm your patch will fix this?
# Before this patch.
# After this patch.
> Federation:We can't access the AM page while using federation
> -------------------------------------------------------------
>
> Key: YARN-10786
> URL: https://issues.apache.org/jira/browse/YARN-10786
> Project: Hadoop YARN
> Issue Type: Bug
> Components: federation
> Affects Versions: 3.2.1
> Reporter: Song Jiacheng
> Priority: Major
> Labels: federation
> Fix For: 3.2.1
>
> Attachments: YARN-10786.v1.patch
>
>
> The reason of this is that AM gets the proxy URI from config
> yarn.web-proxy.address, and if it does not exist, it will get the URI from
> yarn.resourcemanager.webapp.address.
> But in federation, we don't know which RM will be the home cluster of an
> application, so I do this fix:
> 1. Add this config in the yarn-site.xml on client.
> <property>
> <name>yarn.web-proxy.address</name>
> <value>rm1:9088,rm2:9088</value>
> </property>
> 2. Change the way to get the config from Configuration#get to
> Configuration#getStrings in WebAppUtils#getProxyHostsAndPortsForAmFilter.
> So that I can access the AM page now.
> This config need to be added in the client side, so it will affect
> application only.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
