Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 28 Jan 2014 22:15:39 +0000 (UTC)
From: "Arpit Gupta (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12691549.1390874590680.561.1390947339634@arcas>
In-Reply-To: <JIRA.12691549.1390874590680@arcas>
References: <JIRA.12691549.1390874590680@arcas>
Subject: [jira] [Commented] (YARN-1660) add the ability to set
 yarn.resourcemanager.hostname.rm-id instead of setting all the various
 host:port properties for RM
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Arpit Gupta commented on YARN-1660:
-----------------------------------

The way it works in non HA mode is that yarn-default.xml is doing what [~xgong] mentioned above there is no java code that was changed for it. Thus dont think HA code broke it.

> add the ability to set yarn.resourcemanager.hostname.rm-id instead of setting all the various host:port properties for RM
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-1660
>                 URL: https://issues.apache.org/jira/browse/YARN-1660
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Arpit Gupta
>            Assignee: Xuan Gong
>
> Currently the user has to specify all the various host:port properties for RM. We should follow the pattern that we do for non HA setup where we can specify yarn.resourcemanager.hostname.rm-id and the defaults are used for all other affected properties.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)