[
https://issues.apache.org/jira/browse/IGNITE-16161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-16161:
---------------------------------------
Labels: calcite3-required ignite-3 (was: calcite2-required
calcite3-required ignite-3)
> 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: Andrey Mashenkov
> Priority: Blocker
> Labels: calcite3-required, ignite-3
> Fix For: 3.0.0-alpha4
>
> Attachments: image-2021-12-20-14-37-02-163.png, image.png
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> 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)
