Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.6.0
-
None
-
None
Description
Courtesy Thomas Nystrand, we found that on two of our clusters configured with the CapacityScheduler, usedResources occasionally becomes negative.
e.g.
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