[
https://issues.apache.org/jira/browse/YARN-9116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16736552#comment-16736552
]
Weiwei Yang commented on YARN-9116:
-----------------------------------
Hi [~aihuaxu]
{quote}we are still introducing the incompatibility change since the root is
set to 16G {{yarn.scheduler.capacity.root.maximum-allocation-mb=16G}} while the
child queue root.large is set to 80G (larger value).
{quote}
Is that a different behavior than today? If I remember correctly, this is same
as today which sets queue max separately. I have listed the incompatibility in
my last comment,
{quote}this way might introduce a different behavior because the max-allocation
user sets for a queue will be passing to all its child.
{quote}
that's the thing I am concerned with.
{quote}What you are proposing is: the child can override the parent's value
(larger or smaller) but won't exceed the global value, correct?
{quote}
Yes, this is my suggestion. But it would be nice to hear from [~tgraves] as he
initiated added this, also from [~leftnoteasy].
Thanks
> Capacity Scheduler: add the default maximum-allocation-mb and
> maximum-allocation-vcores for the queues
> ------------------------------------------------------------------------------------------------------
>
> Key: YARN-9116
> URL: https://issues.apache.org/jira/browse/YARN-9116
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: capacity scheduler
> Affects Versions: 2.7.0
> Reporter: Aihua Xu
> Assignee: Aihua Xu
> Priority: Major
> Attachments: YARN-9116.1.patch
>
>
> YARN-1582 adds the support of maximum-allocation-mb configuration per queue
> which is targeting to support larger container features on dedicated queues
> (larger maximum-allocation-mb/maximum-allocation-vcores for such queue) .
> While to achieve larger container configuration, we need to increase the
> global maximum-allocation-mb/maximum-allocation-vcores (e.g. 120G/256) and
> then override those configurations with desired values on the queues since
> queue configuration can't be larger than cluster configuration. There are
> many queues in the system and if we forget to configure such values when
> adding a new queue, then such queue gets default 120G/256 which typically is
> not what we want.
> We can come up with a queue-default configuration (set to normal queue
> configuration like 16G/8), so the leaf queues gets such values by default.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
