[
https://issues.apache.org/jira/browse/YARN-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892388#comment-13892388
]
Xuan Gong commented on YARN-1660:
---------------------------------
bq. We should may be move getRMDefaultPortNumber to YarnConfiguration
moved
bq. I would use two different variables for the confKey corresponding to the
RPC-address conf, and the confKey for hostname.
changed
bq. Didn't quite understand why we need the following change:
I was thinking that if we only provide the configurations like
"yarn.resourcemanager.hostname.rm1", and do not provider any RM RPC addresses
configurations. After this patch, we will use the address from
"yarn.resourcemanager.hostname.rm1" and default port as this rm's rpc address.
When we initials RM, the RM will get that piece of information. But, when the
failover happens, if there is no rm rpc address provided in configuration, how
does, for example,yarnclient know which address it should connect to. That is
why I did this change. When it calls getConfKeyForRMInstance, it will build the
RM rpc address based on the RM_ID it providers, then the client could get the
adress.
> add the ability to set yarn.resourcemanager.hostname.rm-id instead of setting
> all the various host:port properties for RM
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: YARN-1660
> URL: https://issues.apache.org/jira/browse/YARN-1660
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Arpit Gupta
> Assignee: Xuan Gong
> Attachments: YARN-1660.1.patch
>
>
> Currently the user has to specify all the various host:port properties for
> RM. We should follow the pattern that we do for non HA setup where we can
> specify yarn.resourcemanager.hostname.rm-id and the defaults are used for all
> other affected properties.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
