[
https://issues.apache.org/jira/browse/YARN-5881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sunil G updated YARN-5881:
--------------------------
Attachment: YARN-5881.v0.patch
Attaching an initial wip patch to cover below cases:
# New configurations for absolute min/max resources. This could be configured
per label as well. Various validations to ensure the configs are acceptable.
# Calculating an effective min resource ration in case cluster is resized.
# Defining a new api called {{getEffectiveMinResource}} in each queue to get
either min resource if configured, or guaranteed capacity in default cases.
This could be used in various parts in scheduler.
ToDo:
# Use of new api in {{getEffectiveMinResource}} in various critical paths in
scheduler.
# Impact on metrics, UI and preemption module
> Enable configuration of queue capacity in terms of absolute resources
> ---------------------------------------------------------------------
>
> Key: YARN-5881
> URL: https://issues.apache.org/jira/browse/YARN-5881
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Sean Po
> Assignee: Wangda Tan
> Attachments:
> YARN-5881.Support.Absolute.Min.Max.Resource.In.Capacity.Scheduler.design-doc.v1.pdf,
> YARN-5881.v0.patch
>
>
> Currently, Yarn RM supports the configuration of queue capacity in terms of a
> proportion to cluster capacity. In the context of Yarn being used as a public
> cloud service, it makes more sense if queues can be configured absolutely.
> This will allow administrators to set usage limits more concretely and
> simplify customer expectations for cluster allocation.
--
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
