[jira] [Assigned] (IGNITE-16161) Memory leak in BaseQueryContext

["Konstantin Orlov (Jira)" <ji...@apache.org>]

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

Konstantin Orlov reassigned IGNITE-16161:
-----------------------------------------

    Assignee: Konstantin Orlov

> Memory leak in BaseQueryContext
> -------------------------------
>
>                 Key: IGNITE-16161
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16161
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>    Affects Versions: 3.0.0-alpha3
>            Reporter: Vyacheslav Koptilin
>            Assignee: Konstantin Orlov
>            Priority: Blocker
>              Labels: ignite-3
>         Attachments: image-2021-12-20-14-37-02-163.png
>
>
> BaseQueryContext contains a number of static fields that are used in order to store references to internal classes. For example, BaseQueryContext.CLUSTER which indirectly refers to ignite tables (TableImpl instances). Unfortunately, these references are not cleared even though the corresponding ignite node is stopped.
> The following trace based on a heap dump illustrates the issue:
>  !image-2021-12-20-14-37-02-163.png! 
> This issue can be partially mitigated by clearing ring buffers in StripedDisruptor, but the right way to fix the issue is a proper approach to handle static collections in BaseQueryContext.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)