[
https://issues.apache.org/jira/browse/YARN-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13839168#comment-13839168
]
Xuan Gong commented on YARN-1325:
---------------------------------
[~ozawa], [~kkambatl] I will start to work on this ticket.
For the HA, since we need multiple RMs, we can just enforce this check. Also,
we can check whether each of RM id in RM-HA-IDs has the configuration for this
list
{RM_ADDRESS,RM_SCHEDULER_ADDRESS,RM_ADMIN_ADDRESS,RM_RESOURCE_TRACKER_ADDRESS,RM_WEBAPP_ADDRESS,RM_WEBAPP_HTTPS_ADDRESS}.
Since those addresses are very important for failover. I think that we need to
enforce those checks, too.
What do you think ?
> RMHAProtocolService#serviceInit should check configuration contains multiple
> RM
> -------------------------------------------------------------------------------
>
> Key: YARN-1325
> URL: https://issues.apache.org/jira/browse/YARN-1325
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Tsuyoshi OZAWA
> Assignee: Xuan Gong
> Labels: ha
>
> Currently, we can enable RM HA configuration without multiple RM
> ids(YarnConfiguration.RM_HA_IDS). This behaviour can cause wrong operations.
> ResourceManager should verify that more than 1 RM id must be specified in
> RM-HA-IDs.
> One idea is to support "strict mode" to enforce this check as
> configuration(e.g. yarn.resourcemanager.ha.strict-mode.enabled).
--
This message was sent by Atlassian JIRA
(v6.1#6144)
