[
https://issues.apache.org/jira/browse/YARN-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889825#comment-13889825
]
Vinod Kumar Vavilapalli commented on YARN-1639:
-----------------------------------------------
bq. Yes, it is possible to return null. But this can be verified in
verifyAndSetCurrentRMHAId(). If getRMHAId() is return null, it will throw out
an exception
Yeah, I checked all the code-paths. This validation happens upfront in the RM
so all the remaining callers are fine. There should be a better way to
structure it, but it seems fine for now.
The patch looks good to me. +1. Checking this in.
> 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
> Attachments: YARN-1639.1.patch, YARN-1639.2.patch, YARN-1639.3.patch,
> YARN-1639.4.patch, YARN-1639.5.patch
>
>
> 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)
