You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@yunikorn.apache.org by "Craig Condit (Jira)" <ji...@apache.org> on 2025/02/13 03:48:00 UTC

[jira] [Closed] (YUNIKORN-3026) Resource overcommit

     [ https://issues.apache.org/jira/browse/YUNIKORN-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Craig Condit closed YUNIKORN-3026.
----------------------------------

> Resource overcommit
> -------------------
>
>                 Key: YUNIKORN-3026
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-3026
>             Project: Apache YuniKorn
>          Issue Type: New Feature
>          Components: core - scheduler
>            Reporter: Rafał Boniecki
>            Priority: Major
>
> Provide implementation of resource (cpu, memory) overcommit.
> Kubernetes requests/limits model promotes waste of a lot of resources. It's impossible to correctly (without wasting resources or resource starvation) set static resources at pod creation. It would be useful for scheduler to have an ability to ignore these requests/limits and schedule by real load instead up to some configured soft limit and when hard limit is hit (eg 60% of real cpu usage and/or 40% of real memory usage) it should have ability to deschedule some pods (configurable which ones eg by presence of annotation) using some kind of algorithm (eg random/highest resource used/lowest resource used, ideally in combination with priority of the pod and or it's labels/annotations).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org