Junping Du commented on YARN-3933:

I think the title here is a bit misleading. Available resource being negative 
shouldn't be a problem (e.g. enabling feature NM resource configuration - 
YARN-291) which means resource are over-commit although we shouldn't see it in 
most of cases. It is actually a race condition bug for FairScheduler, please 
mention it explicitly or developer/user may have impression that resource 
shouldn't be negative in any cases which we never have this assumption.

> 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