[
https://issues.apache.org/jira/browse/YUNIKORN-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865830#comment-17865830
]
Wilfred Spiegelenburg commented on YUNIKORN-2757:
-------------------------------------------------
Not sure this adds anything. Max resources is either set or not. Max resources
of a child can never be more than what is set on the parent. Without taking
usage into account it does not really matter what max is and where it came from.
Lets take an example: I have a hierarchy with 4 levels, level 1 being the root
and level 4 the leaf. A max is set at level 2 only. The root has a dynamic
maximum based on the cluster size. There is no way of interpreting a maximum at
the leaf level 4. What is the impact of that maximum if I do not know what my
queue structure looks like? Do I have 1 or 10 queues at level 3? How many
children has each level 3 queue? Are there any maximums sets at level 3? Are
there any siblings under the parent queue of the level 4 queue I am looking at?
Do sibling queues of my level 4 queue have maximums set or not...
The only time the resolved maximum from the parent would come into play is when
a gang is submitted. We reject the application is it is larger than this
resolved maximum. If that rejections is not clear enough we can improve that.
For scheduling the resolved maximum is also irrelevant. We use the headroom of
a queue to decide if the allocation fits. Current usage linked to maximums
gives the correct picture. That only works at the specific queue level.
> Consider adding new field `resolvedMaxResource` to queue dao to show the true
> limit
> -----------------------------------------------------------------------------------
>
> Key: YUNIKORN-2757
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2757
> Project: Apache YuniKorn
> Issue Type: Improvement
> Reporter: Chia-Ping Tsai
> Priority: Major
>
> The true max resources of queue is based on all parents. It could be hard to
> see/understand the true "max resources" of queue by human eyes if there is a
> huge queue trees.
> Hence, it would be nice to add the "resolved" max resources to restful APIs.
> Also, our UI can leverages the field to help users to understand which max
> resource will be used by this queue
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
