You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@yunikorn.apache.org by "Wilfred Spiegelenburg (Jira)" <ji...@apache.org> on 2020/07/14 12:13:00 UTC
[jira] [Resolved] (YUNIKORN-278) Outstanding requests in queues
with no max capacity set should always trigger auto-scaling
[ https://issues.apache.org/jira/browse/YUNIKORN-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wilfred Spiegelenburg resolved YUNIKORN-278.
--------------------------------------------
Fix Version/s: 0.9
Resolution: Fixed
change committed and backported into branch-0.9
> Outstanding requests in queues with no max capacity set should always trigger auto-scaling
> ------------------------------------------------------------------------------------------
>
> Key: YUNIKORN-278
> URL: https://issues.apache.org/jira/browse/YUNIKORN-278
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
> Reporter: Weiwei Yang
> Assignee: Weiwei Yang
> Priority: Major
> Labels: autoscaling, pull-request-available
> Fix For: 0.9
>
>
> Currently, getMaxHeadRoom() returns nil when capacity is not set, we expect this queue has unlimited capacity; however, resources.FitIn(headRoom, request.AllocatedResource) will always return false in such case
> this causes the problem if the queue has no capacity set, pods will not be set to unschedulable to trigger auto-scaling (we expect this is always setting to unschedulable)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org