[YUNIKORN-1599] Configuration processing should support limit object content check.

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: core - scheduler
• Assignee: Qi Zhu
• Reporter: Qi Zhu
• Created: 24/Feb/23 06:47
• Updated: 09/Sep/24 11:17

Description

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.