[
https://issues.apache.org/jira/browse/IGNITE-10959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17118803#comment-17118803
]
Cong Guo commented on IGNITE-10959:
-----------------------------------
Hi, Maxim
In my case, the fix under IGNITE-11970 does not solve the problem. The entries
are stored in the pending buffer because the current batch does not move on. It
is not a waste like in IGNITE-11970. It is a memory leak. There is no limit on
the pending buffer.
According to another comment above, this issue is relevant to the sync mode and
the backup number. I did not test all the cases, but you can easily reproduce
this issue using three Ignite node with Transactional + Partition + 2 backups.
# Start a 3-node Ignite cluster, and each node has a continuous query to watch
updates in cache.
# Send updates to three nodes continuously. Simple puts are OK.
# Restart one Ignite node, and then memory leak can be seen on two other nodes.
I attach the figure showing the accumulation point and references in my
experiment here.
!referencepath.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
> Assignee: Maxim Muzafarov
> Priority: Critical
> Attachments: CacheContinuousQueryMemoryUsageTest.java,
> CacheContinuousQueryMemoryUsageTest.result,
> CacheContinuousQueryMemoryUsageTest2.java,
> Memory_blowup_in_Ignite_CacheContinuousQueryHandler.txt,
> Memory_blowup_in_Ignite_CacheContinuousQueryHandler.txt,
> Memory_blowup_in_Ignite_CacheContinuousQueryHandler.txt,
> continuousquery_leak_profile.png, referencepath.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)
