hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-853) maximum-am-resource-percent doesn't work after refreshQueues command
Date Tue, 25 Jun 2013 18:59:20 GMT

    [ https://issues.apache.org/jira/browse/YARN-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693277#comment-13693277
] 

Zhijie Shen commented on YARN-853:
----------------------------------

The patch looks almost good, just one small nit: In constructor,
{code}
    this.maxAMResourcePerQueuePercent = 
        cs.getConfiguration().
            getMaximumApplicationMasterResourcePerQueuePercent(getQueuePath());
{code}
maxAMResourcePerQueuePercent is set again in maxAMResourcePerQueuePercent. Though it does
no harm now, it's still good to avoid setting the variable twice.
                
> 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.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