[ https://issues.apache.org/jira/browse/YARN-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774321#comment-17774321 ]
dzcxzl commented on YARN-3933: ------------------------------ Note that branch 2.8 is not consistent with branch 3.0 and branch2.9 fixes. branch 3.0 https://github.com/apache/hadoop/commit/646c6d6509f515b1373288869fb92807fa2ddc9b branch 2.8 https://github.com/apache/hadoop/commit/233252aa9a2f1e2dfc2a5206676b6b8e462d5e7e > 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 > Priority: Major > Labels: oct16-medium > Fix For: 2.8.0, 3.0.0-alpha4 > > 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 (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org