[
https://issues.apache.org/jira/browse/YARN-6197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876771#comment-15876771
]
Wangda Tan commented on YARN-6197:
----------------------------------
I would prefer to keep logic as-is, there're two major purposes of
AM-percentage. a. Avoid all resource in a queue consumed by AM, b. Avoid too
many concurrent apps running.
If we assume AM resource of unmanaged AM to zero, under the same configuration
(by default {{maximum-applications}} set to 10k), there're too many apps can
get started. So it will change the behavior.
And also, under existing logic, LeafQueue skips apps until it find an app can
fit in the available AM resource quota, which makes unmanaged AM get activated
when queue doesn't have free AM resource quota.
> CS Leaf queue am usage gets updated for unmanaged AM
> ----------------------------------------------------
>
> Key: YARN-6197
> URL: https://issues.apache.org/jira/browse/YARN-6197
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Bibin A Chundatt
> Assignee: Bibin A Chundatt
>
> {{LeafQueue#activateApplication()}} for unmanaged AM the am_usage is updated
> with scheduler minimum allocation size. Cluster resource/AM limit headroom
> for other apps in queue will get reduced .
> Solution: FicaScheduler unManagedAM flag can be used to check AM type.
> Based on flag the queueusage need to be updated during activation and removal
> Thoughts??
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
