[
https://issues.apache.org/jira/browse/YUNIKORN-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17848863#comment-17848863
]
Wilfred Spiegelenburg commented on YUNIKORN-2637:
-------------------------------------------------
The case we are solving here is the correct removal of a pod that was
registered and then stopped. In this case if the pod was assigned to a node it
gets removed, this includes from the core also. In the case that it was not
assigned to a node the request gets removed. I think both core and k8shim are
affected by this after looking at the details in YUNIKORN-2526.
So I am not sure if that is the root cause of the difference...
> finalizePods should ignore pods like registerPods does
> ------------------------------------------------------
>
> Key: YUNIKORN-2637
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2637
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: shim - kubernetes
> Reporter: Wilfred Spiegelenburg
> Assignee: Wilfred Spiegelenburg
> Priority: Major
> Labels: pull-request-available
>
> The initialisation code is a two step process for pods: first list all pods
> and add them to the system in registerPods(). This returns a list of pods
> processed.
> The second step happens after event handlers are turned on and nodes have
> been cleaned up etc. During the second step pods from the first step are
> checked and removed. However pods that were already in a terminated state in
> step 1 get removed again. Although the step should be idempotent this is
> unneeded. When iterating over the existing pods any pod in a terminal state
> should be skipped.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
