You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@yunikorn.apache.org by "Wilfred Spiegelenburg (Jira)" <ji...@apache.org> on 2020/07/15 12:55:00 UTC

[jira] [Resolved] (YUNIKORN-282) K8shim may have staled nodes causing problems

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

Wilfred Spiegelenburg resolved YUNIKORN-282.
--------------------------------------------
    Fix Version/s: 0.9
       Resolution: Fixed

Merged the changes into master and branch-0.9

closing as fixed

> K8shim may have staled nodes causing problems
> ---------------------------------------------
>
>                 Key: YUNIKORN-282
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-282
>             Project: Apache YuniKorn
>          Issue Type: Bug
>          Components: shim - kubernetes
>            Reporter: Weiwei Yang
>            Assignee: Weiwei Yang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.9
>
>
> When adding/removing nodes back and force, and nodes are created with same name. In such cases, the shared index informer may trigger Update event instead of an Add (resource key is the same). If the node has stale info in the cache, this will cause the fix we did for YUNIKORN-220 not work. We need to make sure when a node is deleted, the corresponding info is also deleted from the cache.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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