[
https://issues.apache.org/jira/browse/YUNIKORN-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17804782#comment-17804782
]
Craig Condit edited comment on YUNIKORN-2319 at 1/9/24 3:46 PM:
----------------------------------------------------------------
I'm not saying no, just pointing out that a "simple" solution to this issue may
create more problems. If we attempt to optimize this, we need to be very
careful not to introduce concurrency issues.
was (Author: ccondit):
I'm not saying no, just pointing out that a "simple" solution to this issue may
create more. If we attempt to optimize this, we need to be very careful not to
introduce concurrency issues.
> 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
> 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: [email protected]
For additional commands, e-mail: [email protected]
