You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Craig Condit (Jira)" <ji...@apache.org> on 2024/03/05 22:46:00 UTC
[jira] [Resolved] (YUNIKORN-2467) Remove AllocationAsk from the core when a pod is completed
[ https://issues.apache.org/jira/browse/YUNIKORN-2467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Condit resolved YUNIKORN-2467.
------------------------------------
Fix Version/s: 1.5.0
Resolution: Fixed
Merged to master and cherry-picked to branch-1.5.0.
> Remove AllocationAsk from the core when a pod is completed
> ----------------------------------------------------------
>
> Key: YUNIKORN-2467
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2467
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: shim - kubernetes
> Reporter: Peter Bacsko
> Assignee: Peter Bacsko
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.5.0
>
>
> A new issue was discovered while fixing YUNIKORN-2465. This also results in growing memory usage in case of long running applications.
> When a pod reaches a terminal state (Success / Failed), we send an update request from the shim to the core ({{Task.releaseAllocation()}}). However, we only discard the allocation itself and we don't do anything about the ask. It is kept inside the Application object until it becomes Completed.
--
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