Weiwei Yang created YUNIKORN-147:
------------------------------------
Summary: 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
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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org
