You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@yunikorn.apache.org by "Chen Yu Teng (Jira)" <ji...@apache.org> on 2023/04/09 09:09:00 UTC

[jira] [Resolved] (YUNIKORN-1606) Configuration processing should support limit quota check at the same level.

     [ https://issues.apache.org/jira/browse/YUNIKORN-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chen Yu Teng resolved YUNIKORN-1606.
------------------------------------
    Resolution: Fixed

> Configuration processing should support limit quota check at the same level.
> ----------------------------------------------------------------------------
>
>                 Key: YUNIKORN-1606
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1606
>             Project: Apache YuniKorn
>          Issue Type: Sub-task
>            Reporter: Qi Zhu
>            Assignee: Qi Zhu
>            Priority: Major
>              Labels: pull-request-available
>
> No checks are performed for the limits against the queue quotas. This means that as part of the current checks a limit can be set that is higher than the queue would allow. There is also no hierarchical check in place. This means that a child could set higher limits than is possible based on the parent settings.
>  
> The configuration validation processing must be extended to the limit objects. At each level in the configuration the resource quota assigned in a limit must be smaller than the maximum allowed at that level for the queue. The queue quota processing already has this builtin and the limit should be checked against the quota.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org