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 "Wilfred Spiegelenburg (JIRA)" <ji...@apache.org> on 2016/04/20 16:41:25 UTC

[jira] [Updated] (YARN-4971) RM fails to re-bind to wildcard IP after failover in multi homed clusters

     [ https://issues.apache.org/jira/browse/YARN-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wilfred Spiegelenburg updated YARN-4971:
----------------------------------------
    Attachment: YARN-4971.1.patch

patch to not override the bind address in the two services
all tests pass locally, no new test added since we do not have multi homed tests

> 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: 3.0.0
>            Reporter: Wilfred Spiegelenburg
>            Assignee: Wilfred Spiegelenburg
>         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
(v6.3.4#6332)