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

Posted to dev@yunikorn.apache.org by "Craig Condit (Jira)" <ji...@apache.org> on 2023/03/06 16:00:00 UTC

[jira] [Resolved] (YUNIKORN-1622) K8shim: Race in allocate vs pod delete

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

Craig Condit resolved YUNIKORN-1622.
------------------------------------
    Fix Version/s: 1.3.0
       Resolution: Fixed

Merged to master.

> K8shim: Race in allocate vs pod delete
> --------------------------------------
>
>                 Key: YUNIKORN-1622
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1622
>             Project: Apache YuniKorn
>          Issue Type: Bug
>          Components: shim - kubernetes
>    Affects Versions: 1.0.0, 1.1.0, 1.2.0
>            Reporter: Wilfred Spiegelenburg
>            Assignee: Wilfred Spiegelenburg
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 1.3.0
>
>
> When a pod gets deleted at the K8s level and at the same time allocated by the core the pod could be left as allocated in the core until the core gets restarted.
> This is a a long standing bug and affects all versions of YuniKorn even the versions released during incubation.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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