[ https://issues.apache.org/jira/browse/YUNIKORN-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manikandan R updated YUNIKORN-1599: ----------------------------------- Parent Issue: YUNIKORN-2428 (was: YUNIKORN-1544) > Configuration processing should support limit object content check. > ------------------------------------------------------------------- > > Key: YUNIKORN-1599 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1599 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: core - scheduler > Reporter: Qi Zhu > Assignee: Qi Zhu > Priority: Major > > Limits are configured at multiple levels in the hierarchy a fixed order of > enforcement is used. Like with queue quotas, checks start at the leaf queue > and work their way up the hierarchy finishing at the _root_ level. > For the limit configuration processing the same needs to be implemented and > the config should be rejected if it does not comply. Any limit set at any > level below the root _must_ always be smaller or equal to the root limit. > The checks for the limit configuration _must_ be part of the generic > configuration checks currently performed as part of the loading of the > configuration. We cannot allow the configuration to be accepted at the queue > level and later be denied at the limit level checks. A change is all or > nothing, we cannot apply partial changes. Configuration checks must be made > without impacting the scheduling cycles. After the change has passed the > configuration check the changed configuration _must_ then be applied in a > single action. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org