[
https://issues.apache.org/jira/browse/YUNIKORN-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513670#comment-17513670
]
Craig Condit commented on YUNIKORN-1159:
----------------------------------------
This appears to be due to the node coordinator not registering for added pods.
Consequently, their resources are not updated in the core.
> 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
> Assignee: Craig Condit
> Priority: Blocker
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
