[
https://issues.apache.org/jira/browse/YARN-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889083#comment-13889083
]
Xuan Gong commented on YARN-1611:
---------------------------------
bq. Document the config-provider property in yarn-default.xml
ADDED
bq. CapacityScheduler shouldn't check for
YarnConfiguration.DEFAULT_RM_CONFIGURATION_PROVIDER_CLASS to determine if it
should useLocalConfigurationProvider. It should directly compare with
org.apache.hadoop.yarn.LocalConfigurationProvider. This in case the default
changes in future.
CHANGED
bq. TestRMAdminService shouldn't write and delete config files in
fs.getHomeDirectory(). Please use a test-specific directory in target. See
BaseContainerManagerTest for example.
FIXED
bq. And did you already file a ticket for the trunk findBugs warning?
https://issues.apache.org/jira/browse/YARN-1683 is used to track
> Make admin refresh of capacity scheduler configuration work across RM failover
> ------------------------------------------------------------------------------
>
> Key: YARN-1611
> URL: https://issues.apache.org/jira/browse/YARN-1611
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Xuan Gong
> Assignee: Xuan Gong
> Attachments: YARN-1611.1.patch, YARN-1611.10.patch,
> YARN-1611.2.patch, YARN-1611.2.patch, YARN-1611.3.patch, YARN-1611.3.patch,
> YARN-1611.4.patch, YARN-1611.5.patch, YARN-1611.6.patch, YARN-1611.7.patch,
> YARN-1611.8.patch, YARN-1611.9.patch, YARN-1611.9.patch
>
>
> Currently, If we do refresh* for a standby RM, it will failover to the
> current active RM, and do the refresh* based on the local configuration file
> of the active RM.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
