hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-853) maximum-am-resource-percent doesn't work after refreshQueues command
Date Mon, 16 Jun 2014 16:16:04 GMT

     [ https://issues.apache.org/jira/browse/YARN-853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jason Lowe updated YARN-853:
----------------------------

    Fix Version/s: 0.23.11

Thanks, Deveraj!  I committed this to branch-0.23 as well.

> 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
>             Fix For: 2.1.0-beta, 0.23.11
>
>         Attachments: YARN-853-1.patch, YARN-853-2.patch, YARN-853-3.patch, YARN-853-4.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 was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message