hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "zhihai xu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-2315) Should use setCurrentCapacity instead of setCapacity to configure used resource capacity for FairScheduler.
Date Fri, 18 Jul 2014 23:14:09 GMT

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

zhihai xu updated YARN-2315:
----------------------------

    Attachment:     (was: YARN-2315.patch)

> Should use setCurrentCapacity instead of setCapacity to configure used resource capacity
for FairScheduler.
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-2315
>                 URL: https://issues.apache.org/jira/browse/YARN-2315
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: zhihai xu
>            Assignee: zhihai xu
>         Attachments: 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.2#6252)

Mime
View raw message