You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Cong Guo (Jira)" <ji...@apache.org> on 2020/05/21 14:14:00 UTC
[jira] [Commented] (IGNITE-10959) Memory leaks in continuous query
handlers
[ https://issues.apache.org/jira/browse/IGNITE-10959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17113213#comment-17113213 ]
Cong Guo commented on IGNITE-10959:
-----------------------------------
Hi,
Is this issue still open? Is there any patch to fix this issue? I can reproduce this issue by restarting one node in a cluster.
# Start a 3-node Ignite cluster, and each node has a continuous query to watch updates in cache.
# Send updates to three nodes continuously.
# Restart one Ignite node, and then memory leak can be seen on two other nodes.
Based on the heap dump, the memory issue happens in entryBufs of CacheContinuousQueryHandler. I already close the continuous query when I stop the Ignite node. However, the pending buffer on two other nodes still increases when the node starts again. Is there any method to discard the pending buffer when one node (the master node of a continuous query) leaves the cluster?
!ObjectRef.PNG!
> Memory leaks in continuous query handlers
> -----------------------------------------
>
> Key: IGNITE-10959
> URL: https://issues.apache.org/jira/browse/IGNITE-10959
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.7
> Reporter: Denis Mekhanikov
> Priority: Major
> Fix For: 2.9
>
> Attachments: CacheContinuousQueryMemoryUsageTest.java, CacheContinuousQueryMemoryUsageTest.result, CacheContinuousQueryMemoryUsageTest2.java, continuousquery_leak_profile.png
>
>
> Continuous query handlers don't clear internal data structures after cache events are processed.
> A test, that reproduces the problem, is attached.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)