[
https://issues.apache.org/jira/browse/YARN-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258327#comment-15258327
]
Daniel Templeton commented on YARN-4971:
----------------------------------------
I agree on [~rchiang]'s test suggestion.
I'm surprised the patch doesn't break any tests since it changes the behavior
of the {{getBindAddress()}} method, which is used for testing.
I suspect the patch may break with security enabled because the
{{DelegationTokenRenewer.setLocalSecretManagerAndServiceAddr()}} method relies
on {{ClientRMService.getBindAddress()}}. Security code generally doesn't like
non-specific addresses. It would be good to do a thorough test with Kerberos
enabled to verify. I don't know what operation uses
{{DelegationTokenRenewer.setLocalSecretManagerAndServiceAddr()}}, but it
shouldn't be too hard to figure out.
> 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
> 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)
