You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Peter Bacsko (Jira)" <ji...@apache.org> on 2024/08/02 13:17:00 UTC

[jira] [Resolved] (YUNIKORN-2319) cache.Task: reference to old pod object is kept after update

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

Peter Bacsko resolved YUNIKORN-2319.
------------------------------------
    Fix Version/s: 1.6.0
       Resolution: Fixed

> cache.Task: reference to old pod object is kept after update
> ------------------------------------------------------------
>
>                 Key: YUNIKORN-2319
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-2319
>             Project: Apache YuniKorn
>          Issue Type: Bug
>          Components: shim - kubernetes
>            Reporter: Peter Bacsko
>            Assignee: Peter Bacsko
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.6.0
>
>         Attachments: 2024-01-09 134112.png, 2024-01-09 134130.png
>
>
> There is a kind of memory leak in the shim: when the pod is updated, the old pod object is still referenced from Task, so the GC has no chance to remove it (only when the pod terminates).
> See screenshot: task points to version 80199, scheduler cache already has a newer version 81216.
> We have two solutions:
> 1. Update the object in the Task together with the scheduler cache
> 2. Don't store the pointer to the pod, instead, always retrieve it from the scheduler cache



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

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