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 "Rohith Sharma K S (JIRA)" <ji...@apache.org> on 2017/03/08 06:46:38 UTC
[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=15900794#comment-15900794 ]
Rohith Sharma K S edited comment on YARN-6304 at 3/8/17 6:46 AM:
-----------------------------------------------------------------
cc :-/ [~kasha] [~xgong] [~jianhe] do you see any issue in returning from AdminService?
was (Author: rohithsharma):
cc :-/ [~kasha] [~xgong] [~jianhe] do you see any issue with it?
> 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
> 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.
> I think we can skip refreshing configurations on ACTIVE RM. However admin executes refresh command separately which indicates him failure if any.
--
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