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 "Karthik Kambatla (JIRA)" <ji...@apache.org> on 2017/02/13 19:51:42 UTC
[jira] [Commented] (YARN-3933) FairScheduler: Multiple calls to
completedContainer are not safe
[ https://issues.apache.org/jira/browse/YARN-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864304#comment-15864304 ]
Karthik Kambatla commented on YARN-3933:
----------------------------------------
Also committed to branch-2.8. That had a minor conflict that I had to fix, posted the 2.8 diff here.
> 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