[
https://issues.apache.org/jira/browse/YARN-10154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17058429#comment-17058429
]
Clay B. commented on YARN-10154:
--------------------------------
Good points [~sunilg]! I always forget about other resources aside from RAM and
CPU's, so the resource vector approach sounds great.
To confirm this patch would offer support for both required min (minimum share
for preemption) and optional max (capacity constraints) per queue if I read the
code right? If so, then shouldn't there be:
* {{yarn.scheduler.capacity.<queue-path>.leaf-queue-template.min-capacity}} -
mandatory
* {{yarn.scheduler.capacity.<queue-path>.leaf-queue-template.max-capacity}} -
optional
> CS Dynamic Queues cannot be configured with absolute resources
> --------------------------------------------------------------
>
> Key: YARN-10154
> URL: https://issues.apache.org/jira/browse/YARN-10154
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 3.1.3
> Reporter: Sunil G
> Assignee: Manikandan R
> Priority: Major
> Attachments: YARN-10154.001.patch
>
>
> In CS, ManagedParent Queue and its template cannot take absolute resource
> value like
> [memory=8192,vcores=8]
> Thsi Jira is to track and improve the configuration reading module of
> DynamicQueue to support absolute resource values.
>
--
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
