[
https://issues.apache.org/jira/browse/YARN-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863093#comment-15863093
]
Karthik Kambatla commented on YARN-3933:
----------------------------------------
Sorry [~guoshiwei] for not getting to this sooner and thanks
[~miklos.szeg...@cloudera.com] for picking this up back again.
I looked at both patches (v5 and v6); the latter looks simpler to me. The only
downside is the extra updateRootQueueMetrics call, but that is likely best left
for YARN-4809. +1 pending Jenkins.
> 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: fairscheduler
> Affects Versions: 2.7.1
> Reporter: Lavkesh Lahngir
> Assignee: Shiwei Guo
> Labels: oct16-medium
> 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
>
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
