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 2023/05/12 05:57:00 UTC

[jira] [Resolved] (YUNIKORN-1641) Queue tracker object is not cleaned up when a queue is deleted

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

Wilfred Spiegelenburg resolved YUNIKORN-1641.
---------------------------------------------
    Fix Version/s: 1.3.0
       Resolution: Fixed

Removal of the objects is now linked to the decrease call. As soon as nothing is tracked in the object it gets removed. This is also the case for the user and group objects themselves. 

> Queue tracker object is not cleaned up when a queue is deleted
> --------------------------------------------------------------
>
>                 Key: YUNIKORN-1641
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1641
>             Project: Apache YuniKorn
>          Issue Type: Sub-task
>          Components: core - scheduler
>            Reporter: Peter Bacsko
>            Assignee: Qi Zhu
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.3.0
>
>
> Currently, every queue has its own {{QueueTracker}} object which is managed by {{{}ugm.Manager{}}}.
> But when the queue is deleted either by a config change or automatically by the partition manager, the tracker object stays in memory, causing a memory leak.



--
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