hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj K (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-853) maximum-am-resource-percent doesn't work consistently with refreshQueues
Date Thu, 20 Jun 2013 06:56:26 GMT

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

Devaraj K updated YARN-853:
---------------------------

    Attachment: YARN-853.patch
    
> maximum-am-resource-percent doesn't work consistently with refreshQueues
> ------------------------------------------------------------------------
>
>                 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.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

Mime
View raw message