Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Mon, 3 Mar 2014 19:08:26 +0000 (UTC)
From: "Karthik Kambatla (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12695757.1392751530725.4820.1393873706368@arcas>
In-Reply-To: <JIRA.12695757.1392751530725@arcas>
References: <JIRA.12695757.1392751530725@arcas>
Subject: [jira] [Commented] (YARN-1734) RM should get the updated
 Configurations when it transits from Standby to Active
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Karthik Kambatla commented on YARN-1734:
----------------------------------------

I guess the ambiguity stems from the definition of success for {{rmadmin -refresh*}} commands.

I propose adding a config - yarn.resourcemanager.ha.refresh-all-rms. When set, the refresh commands should attempt to refresh on all RMs and fail if it can't - i.e., this should fail when called on the StandbyRM? When cleared, the refresh command should attempt to refresh only on this RM and should succeed as long as the configs are refreshed as early as they are required - i.e., it should be okay to refresh on transition to active and the StandbyRM should also succeed? [~xgong], [~vinodkv] - do you think this captures the behavior well enough and is reasonable? 

> RM should get the updated Configurations when it transits from Standby to Active
> --------------------------------------------------------------------------------
>
>                 Key: YARN-1734
>                 URL: https://issues.apache.org/jira/browse/YARN-1734
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Xuan Gong
>            Assignee: Xuan Gong
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: YARN-1734.1.patch, YARN-1734.2.patch, YARN-1734.3.patch, YARN-1734.4.patch, YARN-1734.5.patch, YARN-1734.6.patch, YARN-1734.7.patch
>
>
> Currently, we have ConfigurationProvider which can support LocalConfiguration, and FileSystemBasedConfiguration. When HA is enabled, and FileSystemBasedConfiguration is enabled, RM can not get the updated Configurations when it transits from Standby to Active


--
This message was sent by Atlassian JIRA
(v6.2#6252)