hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1639) YARM RM HA requires different configs on different RM hosts
Date Mon, 03 Feb 2014 21:57:07 GMT

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

Bikas Saha commented on YARN-1639:
----------------------------------

After this patch, if there are 4 RM's in HA setup, then do we have to enumerate all RM instance
configs in the conf file. ie. for RM Admin Service RPC port we need to have 4 entries suffixed
by each RM id (the values may be identical)? Was this the case earlier too? Or earlier, we
could have specified an single config for RM Admin Service RPC and each RM would use its rm
id to create a suffixed entry in the config from the single config.

> 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
>             Fix For: 2.4.0
>
>         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)

Mime
View raw message