[jira] [Resolved] (YUNIKORN-147) Extensive resource quota management

["Weiwei Yang (Jira)" <ji...@apache.org>]

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

Weiwei Yang resolved YUNIKORN-147.
----------------------------------
    Fix Version/s: 0.11
       Resolution: Fixed

> Extensive resource quota management
> -----------------------------------
>
>                 Key: YUNIKORN-147
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-147
>             Project: Apache YuniKorn
>          Issue Type: New Feature
>          Components: core - cache, core - common, core - scheduler, scheduler-interface, shim - kubernetes
>            Reporter: Weiwei Yang
>            Assignee: Weiwei Yang
>            Priority: Major
>             Fix For: 0.11
>
>
> Today, in K8s. The resource quota is enforced by the quota admission controller. Resource quota is charged once a pod is *created* in a namespace, no matter it is running, pending (a pod only consumes resources when it is running), failed, or completed. The admission controller will reject further pods if all quota is exceeded.
> When we run batch workloads with such quota, this can lead to some issues. Let's use Spark as an example: Spark job pods could be pending for many reasons, volume not ready, picky on a host, etc. Such pending pods will consume the resource quota. And subsequentially causing the resources can not be efficiently used.
> The solution is to leverage YuniKorn elastic queues for quota management. Such elastic nature will be helpful to provide efficient resource sharing for batch workloads.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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