hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3933) FairScheduler: Multiple calls to completedContainer are not safe
Date Mon, 13 Feb 2017 20:02:41 GMT

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

Hudson commented on YARN-3933:
------------------------------

ABORTED: Integrated in Jenkins build Hadoop-trunk-Commit #11240 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/11240/])
YARN-3933. FairScheduler: Multiple calls to completedContainer are not (kasha: rev 646c6d6509f515b1373288869fb92807fa2ddc9b)
* (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FSAppAttempt.java
* (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/TestFairScheduler.java


> FairScheduler: Multiple calls to completedContainer are not safe
> ----------------------------------------------------------------
>
>                 Key: YARN-3933
>                 URL: https://issues.apache.org/jira/browse/YARN-3933
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: fairscheduler
>    Affects Versions: 2.7.1
>            Reporter: Lavkesh Lahngir
>            Assignee: Shiwei Guo
>              Labels: oct16-medium
>             Fix For: 2.8.0, 3.0.0-alpha3
>
>         Attachments: YARN-3933.001.patch, YARN-3933.002.patch, YARN-3933.003.patch, YARN-3933.004.patch,
YARN-3933.005.patch, YARN-3933.006.patch, yarn-3933-branch-2.8.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.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message