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 "Ravi Prakash (JIRA)" <ji...@apache.org> on 2017/07/10 23:33:00 UTC
[jira] [Updated] (YARN-6378) Negative usedResources memory in
CapacityScheduler
[ https://issues.apache.org/jira/browse/YARN-6378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ravi Prakash updated YARN-6378:
-------------------------------
Target Version/s: 2.8.2 (was: 2.8.1)
> Negative usedResources memory in CapacityScheduler
> --------------------------------------------------
>
> Key: YARN-6378
> URL: https://issues.apache.org/jira/browse/YARN-6378
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacity scheduler, resourcemanager
> Affects Versions: 2.6.0
> Reporter: Ravi Prakash
> Assignee: Ravi Prakash
>
> Courtesy Thomas Nystrand, we found that on two of our clusters configured with the CapacityScheduler, usedResources occasionally becomes negative.
> e.g.
> {code}
> 2017-03-15 11:10:09,449 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue: assignedContainer application attempt=appattempt_1487222361993_17177_000001 container=Container: [ContainerId: container_1487222361993_17177_01_000014, NodeId: <SOMENODE>:27249, NodeHttpAddress: <SOMENODE>:8042, Resource: <memory:6656, vCores:1>, Priority: 2, Token: null, ] queue=<somequeuename>: capacity=0.2, absoluteCapacity=0.2, usedResources=<memory:-1024, vCores:3>, usedCapacity=0.03409091, absoluteUsedCapacity=0.006818182, numApps=1, numContainers=3 clusterResource=<memory:1249280, vCores:440> type=RACK_LOCAL
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org