hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xuan Gong (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1325) Enabling HA should check Configuration contains multiple RMs
Date Tue, 10 Dec 2013 00:46:08 GMT

    [ https://issues.apache.org/jira/browse/YARN-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843771#comment-13843771

Xuan Gong commented on YARN-1325:

bq.verifyAndSetAllRpcAddresses -> verifyAndSetAllServiceAddresses


bq.Make YarnConfiguration.RM_RPC_ADDRESS_CONF_KEYS @Private




bq.excapeRPCAddressVerification can be completely removed if you change RM_RPC_ADDRESS_CONF_KEYS
itself to depend on HttpConfig.isSecure. Right?


The new patch will focus on checking Configuration contains multiple RMs only. 
Checking the Configuration that the RM service addresses configurations have been set for
all of RM_Ids will be done on YARN-1485.

> Enabling HA should check Configuration contains multiple RMs
> ------------------------------------------------------------
>                 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
>         Attachments: YARN-1325.1.patch, YARN-1325.2.patch, YARN-1325.3.patch
> 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

View raw message