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 "Song Jiacheng (Jira)" <ji...@apache.org> on 2021/05/31 08:46:00 UTC

[jira] [Comment Edited] (YARN-10786) Federation:We can't access the AM page while using federation

    [ https://issues.apache.org/jira/browse/YARN-10786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354305#comment-17354305 ] 

Song Jiacheng edited comment on YARN-10786 at 5/31/21, 8:45 AM:
----------------------------------------------------------------

[~zhengchenyu] Thanks for the comment.

I set yarn.web-proxy.address to all the subcluster webapp addresses, so that all the subcluster can access the AM pages.

I have thought about other solutions, but all of them change a lot and may break some other rules.


was (Author: song jiacheng):
[~zhengchenyu] Thanks for the comment.
{panel:title=我的标题}
In the other way, If we have more than one subcluster, this way may be not good.
{panel}
I set yarn.web-proxy.address to all the subcluster webapp addresses, so that all the subcluster can access the AM pages.

I have thought about other solutions, but all of them change a lot and may break some other rules.

> 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, n_v25156273211c049f8b396dcf15fcd9a84.png, v1.1_dataplat_Hadoop平台_HDP3_2_1版本升级_YARN_26_Federation严重BUG--无法查看AM_WebHome_1621584160759-478.png
>
>
> 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 needs to be added in the client side, so it will affect application only.
> Before fixing, click the AM link in RM or Router:
> !v1.1_dataplat_Hadoop平台_HDP3_2_1版本升级_YARN_26_Federation严重BUG--无法查看AM_WebHome_1621584160759-478.png!
>  And after the fix, we can access the AM page as normal...
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org