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

Posted to issues@yunikorn.apache.org by "Craig Condit (Jira)" <ji...@apache.org> on 2022/03/28 21:52:00 UTC

[jira] [Created] (YUNIKORN-1159) Node occupied resources are not detected on YuniKorn startup

Craig Condit created YUNIKORN-1159:
--------------------------------------

             Summary: Node occupied resources are not detected on YuniKorn startup
                 Key: YUNIKORN-1159
                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1159
             Project: Apache YuniKorn
          Issue Type: Bug
          Components: shim - kubernetes
            Reporter: Craig Condit


When YuniKorn starts up on a Kubernetes cluster, the occupied resources of existing nodes are not properly detected. This can lead to YuniKorn over-allocating resources on a node and resulting in a failure of pods to schedule.

Restarting a pod on a node will cause the occupied values of the node to refresh properly.

 



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

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