Shiwei Guo commented on YARN-3933:

I think so, and so is 
[YRAN-4045|https://issues.apache.org/jira/browse/YARN-4045]. The negative value 
in root queue is casued by call to updateRootQueueMetrics on same containerId. 
In our cluster, it has the ability to run 13000+ container, but the WEB UI says 

- Containers Running: -26546
- Memory Used: -82.38 TB
- VCores Used: -26451

Lucky that it haven't affect scheduling yet.

> Resources(both core and memory) are being negative
> --------------------------------------------------
>                 Key: YARN-3933
>                 URL: https://issues.apache.org/jira/browse/YARN-3933
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.5.2
>            Reporter: Lavkesh Lahngir
>            Assignee: Lavkesh Lahngir
>              Labels: patch
>         Attachments: patch.BUGFIX-JIRA-YARN-3933.txt
> In our cluster we are seeing available memory and cores being negative. 
> Initial inspection:
> Scenario no. 1: 
> In capacity scheduler the method allocateContainersToNode() checks if 
> there are excess reservation of containers for an application, and they are 
> no longer needed then it calls queue.completedContainer() which causes 
> resources being negative. And they were never assigned in the first place. 
> I am still looking through the code. Can somebody suggest how to simulate 
> excess containers assignments ?

This message was sent by Atlassian JIRA

Reply via email to