[
https://issues.apache.org/jira/browse/IGNITE-25449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-25449:
---------------------------------------
Ignite Flags: Release Notes Required (was: Docs Required,Release Notes
Required)
> Investigate Potential Memory Leak in HeavyQueriesTracker (Apache Ignite
> 2.17.0)
> -------------------------------------------------------------------------------
>
> Key: IGNITE-25449
> URL: https://issues.apache.org/jira/browse/IGNITE-25449
> Project: Ignite
> Issue Type: Task
> Affects Versions: 2.17
> Reporter: Oleg Valuyskiy
> Assignee: Oleg Valuyskiy
> Priority: Major
> Labels: ise
> Fix For: 2.18
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Following the upgrade from Apache Ignite 2.16.0 to 2.17.0, a significant
> increase in JVM heap memory consumption was observed, with ~80% (600MB)
> attributed to {{{}HeavyQueriesTracker{}}}'s {{{}ConcurrentHashMap{}}}.
> Analysis suggests suspended {{TrackableQuery}} instances are never removed,
> causing unbounded map growth.
> [https://github.com/apache/ignite/issues/12067]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)