[
https://issues.apache.org/jira/browse/YARN-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13883863#comment-13883863
]
Xuan Gong commented on YARN-1639:
---------------------------------
My proposal:
1. yarn.resourcemanager.ha.id will become optional.
2. When RM starts(if ha.id is not specified), it will automatically figure out
its rm_id by using checking whether RM_ADDRESS is matched with its local
address. For example, the RM local_address is 1.1.1.1, and we have
configuration for yarn.resourcemanager.address_rm2 is 1.1.1.1. So, this rm can
figure out its rm_id as rm2. (There is an assumption here. One node can only
launch one RM.)
3. We can still explicitly specify the ha.id. If this value is explicitly
specified, the rm can use this value directly. It is mostly for testing
purpose, such as MiniYarnCluster, etc.
> YARM RM HA requires different configs on different RM hosts
> -----------------------------------------------------------
>
> Key: YARN-1639
> URL: https://issues.apache.org/jira/browse/YARN-1639
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Arpit Gupta
> Assignee: Xuan Gong
>
> We need to set yarn.resourcemanager.ha.id to rm1 or rm2 based on which rm you
> want to first or second.
> This means we have different configs on different RM nodes. This is unlike
> HDFS HA where the same configs are pushed to both NN's and it would be better
> to have the same setup for RM as this would make installation and managing
> easier.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
