[
https://issues.apache.org/jira/browse/YARN-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13918433#comment-13918433
]
Xuan Gong commented on YARN-1734:
---------------------------------
So, if the Standby RM transits to Active, it will pick the latest
configuration.
For calling refresh* in standby RM, it will throw a standbyException and
trigger the retry. In that case, even if we call refresh* in Standby RM, it
actually do the refresh* in active RM.
bq. With the current code, the Standby would throw a StandbyException, thereby
telling the user that the config refresh has failed. This is not exactly true,
because the Standby would actually pick the latest configs when transitioning
to Active. No?
When RM is at Standby state, all of the active services have already been
stopped. I think this "pick the latest configs" should mean all the related
services pick the latest configs, such as CapacityScheduler, NodesListManager,
ClientRMService, ResourceTrackerService, etc. But since most of these services
are stopped in standby mode, they can not get the latest configurations.
> 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)
