[
https://issues.apache.org/jira/browse/YARN-6304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15971798#comment-15971798
]
Hudson commented on YARN-6304:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11594 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/11594/])
YARN-6304. Skip rm.transitionToActive call to RM if RM is already (junping_du:
rev 6ed9d362242d36bfae4083bf3b1c2eb32fbb2f72)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/AdminService.java
> 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.8.1, 3.0.0-alpha3
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
