[
https://issues.apache.org/jira/browse/YARN-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823607#comment-13823607
]
Karthik Kambatla commented on YARN-1411:
----------------------------------------
In the cluster tests, the NM was coming up at the default port (0) and not the
specified port. I checked the RM-specific ports and made sure they were all
correct but missed the NM ports. Thanks to [~wypoon], we found this problem in
further QE.
> HA config shouldn't affect NodeManager RPC addresses
> ----------------------------------------------------
>
> Key: YARN-1411
> URL: https://issues.apache.org/jira/browse/YARN-1411
> Project: Hadoop YARN
> Issue Type: Sub-task
> Affects Versions: 2.3.0
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
> Priority: Critical
> Labels: ha
> Attachments: yarn-1411-1.patch, yarn-1411-2.patch
>
>
> When HA is turned on, {{YarnConfiguration#getSoketAddress()}} fetches
> rpc-addresses corresponding to the specified rm-id. This should only be for
> RM rpc-addresses. Other confs, like NM rpc-addresses shouldn't be affected by
> this.
> Currently, the NM address settings in yarn-site.xml aren't reflected in the
> actual ports.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
