You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "zhihai xu (JIRA)" <ji...@apache.org> on 2014/08/21 08:04:51 UTC
[jira] [Updated] (YARN-2315) Should use setCurrentCapacity instead
of setCapacity to configure used resource capacity for FairScheduler.
[ https://issues.apache.org/jira/browse/YARN-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
zhihai xu updated YARN-2315:
----------------------------
Attachment: YARN-2315.001.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.001.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.2#6252)