[
https://issues.apache.org/jira/browse/YARN-6378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15968398#comment-15968398
]
Ravi Prakash commented on YARN-6378:
------------------------------------
>From what I can tell, there's an app : {{application_1487222361993_12379}}
>which was moved first from interactive to the production queue, and then from
>production queue to the etl queue . This was a massive application so I'm not
>sure if the discrepancy in accounting is an artifact of the application being
>moved twice of it being a massive app and some race condition being triggered.
>Or if this application's shenanigans were at all involved ;-)
> 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.7.2
> Reporter: Ravi Prakash
> Assignee: Ravi Prakash
>
> Courtesy Thomas Nystrand, we found that on one 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.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
