[ https://issues.apache.org/jira/browse/YARN-8434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16537902#comment-16537902 ]
Bibin A Chundatt edited comment on YARN-8434 at 7/10/18 2:34 AM: ----------------------------------------------------------------- Thanks [~subru] for explanation While trying out federation i had similar deployment as you mentioned. As mentioned earlier, in federation setup *NodeManager* we are supposed to configure {{yarn.client.failover-proxy-provider=org.apache.hadoop.yarn.server.federation.failover.FederationRMFailoverProxyProvider}} , as per documentation. {{yarn.client.failover-proxy-provider}} configuration is used by ServerRMProxy in same NodeManager for {{ResoruceTracker}} communication too . {{FederationRMFailoverProxyProvider}} doesnt have implementation handling {{ResoruceTracker}}. Registration of NM fails in this case .. Hoping the configuration is correct . was (Author: bibinchundatt): [~subru] While trying out federation i had similar deployment as you mentioned. As mentioned earlier, in federation setup NodeManager we are supposed to configure {{yarn.client.failover-proxy-provider=org.apache.hadoop.yarn.server.federation.failover.FederationRMFailoverProxyProvider}} rt ?? > Nodemanager not registering to active RM in federation > ------------------------------------------------------ > > Key: YARN-8434 > URL: https://issues.apache.org/jira/browse/YARN-8434 > Project: Hadoop YARN > Issue Type: Bug > Reporter: Bibin A Chundatt > Assignee: Bibin A Chundatt > Priority: Blocker > Attachments: YARN-8434.001.patch, YARN-8434.002.patch > > > FederationRMFailoverProxyProvider doesn't handle connecting to active RM. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org