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 "Devaraj K (JIRA)" <ji...@apache.org> on 2013/07/10 08:23:49 UTC
[jira] [Commented] (YARN-853) maximum-am-resource-percent doesn't
work after refreshQueues command
[ https://issues.apache.org/jira/browse/YARN-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13704253#comment-13704253 ]
Devaraj K commented on YARN-853:
--------------------------------
[~zjshen], could you check the latest patch when you find some time, Thnx.
> maximum-am-resource-percent doesn't work after refreshQueues command
> --------------------------------------------------------------------
>
> Key: YARN-853
> URL: https://issues.apache.org/jira/browse/YARN-853
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacityscheduler
> Affects Versions: 3.0.0, 2.1.0-beta, 2.0.5-alpha
> Reporter: Devaraj K
> Assignee: Devaraj K
> Attachments: YARN-853-1.patch, YARN-853-2.patch, YARN-853.patch
>
>
> If we update yarn.scheduler.capacity.maximum-am-resource-percent / yarn.scheduler.capacity.<queue-path>.maximum-am-resource-percent configuration and then do the refreshNodes, it uses the new config value to calculate Max Active Applications and Max Active Application Per User. If we add new node after issuing 'rmadmin -refreshQueues' command, it uses the old maximum-am-resource-percent config value to calculate Max Active Applications and Max Active Application Per User.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira