[
https://issues.apache.org/jira/browse/YARN-10169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17247954#comment-17247954
]
zhuqi commented on YARN-10169:
------------------------------
[~leftnoteasy]
I look into the source code, and test locally, we allow the scheduler max
capacity like:
a.max (absolute), a1.max (percentage), a2.max (absolute), a2_1.max (percentage).
We calculate percentage below absolute, when update absolute resources from
parent:
{code:java}
float maxCapacity = queueCapacities.getMaximumCapacity(label);
if (maxCapacity > 0f) {
queueCapacities.setAbsoluteMaximumCapacity(label, maxCapacity * (
parentQueueCapacities == null ?
1 :
parentQueueCapacities.getAbsoluteMaximumCapacity(label)));
}
{code}
When a2.max (absolute) updated to AbsoluteMaximumCapacity, a2_1.max (percentage
below absolute) will be calculated and update for children.
And we need add document for this configuration.
Thanks.
> Mixed absolute resource value and percentage-based resource value in
> CapacityScheduler should fail
> --------------------------------------------------------------------------------------------------
>
> Key: YARN-10169
> URL: https://issues.apache.org/jira/browse/YARN-10169
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Wangda Tan
> Assignee: zhuqi
> Priority: Blocker
> Attachments: YARN-10169.001.patch, YARN-10169.002.patch,
> YARN-10169.003.patch
>
>
> To me this is a bug: if there's a queue has capacity set to float, and
> maximum-capacity set to absolute value. Existing logic allows the behavior.
> For example:
> {code:java}
> queue.capacity = 0.8
> queue.maximum-capacity = [mem=x, vcore=y] {code}
> We should throw exception when configured like this.
--
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
