You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Akira Ajisaka (JIRA)" <ji...@apache.org> on 2017/05/30 06:28:04 UTC
[jira] [Updated] (YARN-6304) Skip rm.transitionToActive call to RM
if RM is already active.
[ https://issues.apache.org/jira/browse/YARN-6304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Akira Ajisaka updated YARN-6304:
--------------------------------
Fix Version/s: 2.9.0
> Skip rm.transitionToActive call to RM if RM is already active.
> ---------------------------------------------------------------
>
> Key: YARN-6304
> URL: https://issues.apache.org/jira/browse/YARN-6304
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Reporter: Rohith Sharma K S
> Assignee: Rohith Sharma K S
> Fix For: 2.9.0, 2.8.1, 3.0.0-alpha4
>
> Attachments: YARN-6304.0001.patch
>
>
> When elector elects RM to become active, even though RM is already in ACTIVE state AdminService does refresh on following configurations.
> # refreshAdminAcls
> # refreshAll to update the configurations.
> But ideally even these operations are need NOT to be done and can be skipped refreshing configurations on ACTIVE RM. However admin executes refresh command separately if there is any config changes to be done.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org