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

Wangda Tan commented on YARN-4971:
----------------------------------

I think we should revisit the patch based on comment from Karthik: 
https://issues.apache.org/jira/browse/YARN-4971?focusedCommentId=15281097&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15281097

I also don't quite understand why the following methods of ClientRMService are 
different: 

One is:
{code:java}
  InetSocketAddress getBindAddress(Configuration conf) {
    return conf.getSocketAddr(
            YarnConfiguration.RM_BIND_HOST,
            YarnConfiguration.RM_ADDRESS,
            YarnConfiguration.DEFAULT_RM_ADDRESS,
            YarnConfiguration.DEFAULT_RM_PORT);
  } {code}
 

And another one is: 
{code:java}
     clientBindAddress = conf.updateConnectAddr(YarnConfiguration.RM_BIND_HOST,
                                               YarnConfiguration.RM_ADDRESS,
                                               
YarnConfiguration.DEFAULT_RM_ADDRESS,
                                               
server.getListenerAddress());{code}
 

Basically, in serviceInit and serviceStart, how to get RM address is different. 
Is that a potential root cause of the problem? [~wilfreds], [~shuzirra]

> RM fails to re-bind to wildcard IP after failover in multi homed clusters
> -------------------------------------------------------------------------
>
>                 Key: YARN-4971
>                 URL: https://issues.apache.org/jira/browse/YARN-4971
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.7.2
>            Reporter: Wilfred Spiegelenburg
>            Assignee: Wilfred Spiegelenburg
>            Priority: Major
>         Attachments: YARN-4971.1.patch
>
>
> If the RM has the {{yarn.resourcemanager.bind-host}} set to 0.0.0.0 the first 
> time the service becomes active binding to the wildcard works as expected. If 
> the service has transitioned from active to standby and then becomes active 
> again after failovers the service only binds to one of the ip addresses.
> There is a difference between the services inside the RM: it only seem to 
> happen for the services listening on ports: 8030 and 8032



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

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

Reply via email to