[
https://issues.apache.org/jira/browse/YARN-8127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433631#comment-16433631
]
Hudson commented on YARN-8127:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13968 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/13968/])
YARN-8127. Resource leak when async scheduling is enabled. Contributed (wwei:
rev 7eb783e2634d8c11fb646f1f2fdf597336325312)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestCapacitySchedulerAsyncScheduling.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/common/fica/FiCaSchedulerApp.java
> Resource leak when async scheduling is enabled
> ----------------------------------------------
>
> Key: YARN-8127
> URL: https://issues.apache.org/jira/browse/YARN-8127
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Weiwei Yang
> Assignee: Tao Yang
> Priority: Critical
> Fix For: 3.2.0, 3.1.1
>
> Attachments: YARN-8127.001.patch, YARN-8127.002.patch,
> YARN-8127.003.patch, YARN-8127.004.patch
>
>
> Brief steps to reproduce
> # Enable async scheduling, 5 threads
> # Submit a lot of jobs trying to exhaust cluster resource
> # After a while, observed NM allocated resource is more than resource
> requested by allocated containers
> Looks like the commit phase is not sync handling reserved containers, causing
> some proposal incorrectly accepted, subsequently resource was deducted
> multiple times for a container.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
