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 "Eric Payne (Jira)" <ji...@apache.org> on 2021/10/04 20:08:00 UTC
[jira] [Reopened] (YARN-8127) Resource leak when async scheduling
is enabled
[ https://issues.apache.org/jira/browse/YARN-8127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Payne reopened YARN-8127:
------------------------------
Attched branch-2.10 patch. Reopening and putting in PATCH AVAILABLE state to kick the prec-mmit build.
The backport is clean except for a couple of minor unit test changes.
If all goes well, I will cherry-pick back to 2.10 and fixup the unit test there.
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org