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 "Shiwei Guo (JIRA)" <ji...@apache.org> on 2015/09/07 08:56:46 UTC

[jira] [Commented] (YARN-3933) Race condition when calling AbstractYarnScheduler.completedContainer.

    [ https://issues.apache.org/jira/browse/YARN-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14733301#comment-14733301 ] 

Shiwei Guo commented on YARN-3933:
----------------------------------

Excuse me, Junping, I'm wondering what to do next about this patch, to mark it as resolved using the 'Resolve Issue' button? It works fine on our production cluster.

> Race condition when calling AbstractYarnScheduler.completedContainer.
> ---------------------------------------------------------------------
>
>                 Key: YARN-3933
>                 URL: https://issues.apache.org/jira/browse/YARN-3933
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.6.0, 2.7.0, 2.5.2, 2.7.1
>            Reporter: Lavkesh Lahngir
>            Assignee: Shiwei Guo
>              Labels: patch
>         Attachments: YARN-3933.001.patch
>
>
> 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
(v6.3.4#6332)