[
https://issues.apache.org/jira/browse/YUNIKORN-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17705796#comment-17705796
]
Wilfred Spiegelenburg commented on YUNIKORN-1658:
-------------------------------------------------
The changes for the BestEfofort pods as per YUNIKORN-1632 should be applied on
top of these changes while testing and deploying. Without these changes the
placeholders might not trigger scale up.
> autoscaling is not triggered for requests with unlimited resources
> ------------------------------------------------------------------
>
> Key: YUNIKORN-1658
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1658
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
> Affects Versions: 1.0.0, 1.1.0, 1.2.0
> Reporter: Wilfred Spiegelenburg
> Assignee: Wilfred Spiegelenburg
> Priority: Critical
>
> Auto scaling is triggered by marking pods as unschedulable. The core triggers
> the checks to mark pods unschedulable. The checks is based on the maximum
> resource quotas for the queues and the requested resources.
> The number of requests to mark outstanding can never exceed the resources
> amount available within the quota for the queues.
> If a request has unlimited resource types in a limited queue scale up will
> not be triggered due to failures in the headroom calculation. The headroom
> calculation for the resource type that is not limited will become negative.
> This then breaks the "fit in" check as the unlimited resource is now defined
> as a negative value.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
