[
https://issues.apache.org/jira/browse/YUNIKORN-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17791844#comment-17791844
]
Peter Bacsko commented on YUNIKORN-2212:
----------------------------------------
"Second point: In a on-premise cluster we do not want/need to mark the pods for
autoscaling. We should be able to turn this off completely if not needed."
This is completely legit.
"We also do not keep state for all of the asks that have triggered upscaling.
If we have checked the ask and marked it for autoscaling why do we do it again,
and again?"
And let's say there is no node due to missing tolerations... we still trigger
it, right? This doesn't sound good either.
> Request should not be outstanding if scheduling has not been attempted
> ----------------------------------------------------------------------
>
> Key: YUNIKORN-2212
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2212
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
> Reporter: Peter Bacsko
> Assignee: Peter Bacsko
> Priority: Major
> Labels: pull-request-available
> Attachments: outstandingRequests-1.png
>
>
> In every second, we collect "outstanding requests", ie those which cannot be
> scheduled.
> Problem is, the scheduling cycle might not even tried to schedule those pods.
> If that's the case, we mistakenly set them to "Unschedulable", which can
> trigger autoscaling if the cluster autoscaler happens to run at the beginning
> of the next scan interval.
> Another thing to consider is when we need to mark them as Unschedulable. Eg.
> tryPreemption() succeeded, do we still need new nodes? This can addressed in
> a separate JIRA.
> This issue also shows up during performance testing. Since we submit a lot of
> pods to Yunikorn, {{Scheduler.inspectOutstandingRequests()}} finds&collects
> them and subsequently generates a lot of API server updates. This is a
> special edge case, but on busy clusters, something similar can happen.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
