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

ASF GitHub Bot commented on YARN-2162:
--------------------------------------

Github user kambatla commented on a diff in the pull request:

    https://github.com/apache/hadoop/pull/261#discussion_r134264187
  
    --- Diff: 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/AllocationFileLoaderService.java
 ---
    @@ -605,13 +606,15 @@ private void loadQueue(String parentName, Element 
element,
     
         queueAcls.put(queueName, acls);
         resAcls.put(queueName, racls);
    -    if (maxQueueResources.containsKey(queueName) &&
    -        minQueueResources.containsKey(queueName)
    -        && !Resources.fitsIn(minQueueResources.get(queueName),
    -            maxQueueResources.get(queueName))) {
    +    ResourceConfiguration maxResourceConf = 
maxQueueResources.get(queueName);
    +    if (maxResourceConf != null &&
    +        !maxResourceConf.isPercentage() &&
    --- End diff --
    
    A warning is necessary even when the config is percentage-based. I would 
argue the warning is more important in this case than the other. 


> add ability in Fair Scheduler to optionally configure maxResources in terms 
> of percentage
> -----------------------------------------------------------------------------------------
>
>                 Key: YARN-2162
>                 URL: https://issues.apache.org/jira/browse/YARN-2162
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: fairscheduler, scheduler
>            Reporter: Ashwin Shankar
>            Assignee: Yufei Gu
>              Labels: scheduler
>         Attachments: YARN-2162.001.patch, YARN-2162.002.patch
>
>
> minResources and maxResources in fair scheduler configs are expressed in 
> terms of absolute numbers X mb, Y vcores. 
> As a result, when we expand or shrink our hadoop cluster, we need to 
> recalculate and change minResources/maxResources accordingly, which is pretty 
> inconvenient.
> We can circumvent this problem if we can optionally configure these 
> properties in terms of percentage of cluster capacity. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to