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

Hudson commented on YARN-2315:
------------------------------

SUCCESS: Integrated in Hadoop-Hdfs-trunk #1939 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1939/])
YARN-2315. FairScheduler: Set current capacity in addition to capacity. (Zhihai 
Xu via kasha) (kasha: rev a9a0cc3679432774154a07d3157ffa0a43e0bf01)
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/TestFairScheduler.java
* hadoop-yarn-project/CHANGES.txt
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FSQueue.java


> FairScheduler: Set current capacity in addition to capacity
> -----------------------------------------------------------
>
>                 Key: YARN-2315
>                 URL: https://issues.apache.org/jira/browse/YARN-2315
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: zhihai xu
>            Assignee: zhihai xu
>             Fix For: 2.7.0
>
>         Attachments: YARN-2315.001.patch, YARN-2315.002.patch, 
> YARN-2315.003.patch, YARN-2315.patch
>
>
> Should use setCurrentCapacity instead of setCapacity to configure used 
> resource capacity for FairScheduler.
> In function getQueueInfo of FSQueue.java, we call setCapacity twice with 
> different parameters so the first call is overrode by the second call. 
>     queueInfo.setCapacity((float) getFairShare().getMemory() /
>         scheduler.getClusterResource().getMemory());
>     queueInfo.setCapacity((float) getResourceUsage().getMemory() /
>         scheduler.getClusterResource().getMemory());
> We should change the second setCapacity call to setCurrentCapacity to 
> configure the current used capacity.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to