[
https://issues.apache.org/jira/browse/YARN-8127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424650#comment-17424650
]
Eric Payne commented on YARN-8127:
----------------------------------
Also, FWIW, all tests that ran passed:
{noformat}
[INFO] Results:
[INFO]
[WARNING] Tests run: 2173, Failures: 0, Errors: 0, Skipped: 8
[INFO]
{noformat}
I'll backport this afternoon.
> 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, YARN-8127.branch-2.10.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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
