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/09/07 17:52:00 UTC
[jira] [Updated] (YARN-10935) AM Total Queue Limit goes below
per-user AM Limit if parent is full.
[ https://issues.apache.org/jira/browse/YARN-10935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Payne updated YARN-10935:
------------------------------
Summary: AM Total Queue Limit goes below per-user AM Limit if parent is full. (was: AM Total Queue Limit goes below per-uwer AM Limit if parent is full.)
> AM Total Queue Limit goes below per-user AM Limit if parent is full.
> --------------------------------------------------------------------
>
> Key: YARN-10935
> URL: https://issues.apache.org/jira/browse/YARN-10935
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacity scheduler, capacityscheduler
> Reporter: Eric Payne
> Assignee: Eric Payne
> Priority: Major
>
> This happens when DRF is enabled and all of one resource is consumed but the second resources still has plenty available.
> This is reproduceable by setting up a parent queue where the capacity and max capacity are the same, with 2 or more sub-queues whose max capacity is 100%.
> In one of the sub-queues, start a long-running app that consumes all resources in the parent queue's hieararchy. This app will consume all of the memory but not vary many vcores (for example)
> In a second queue, submit an app. The *{{Max Application Master Resources Per User}}* limit is much more than the *{{Max Application Master Resources}}* limit.
--
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