[
https://issues.apache.org/jira/browse/IGNITE-10959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16973903#comment-16973903
]
Zane Hu commented on IGNITE-10959:
----------------------------------
In addition to having an upper-bound limit to flush and remove 10% events out
from CacheContinuousQueryEventBuffer.pending if the limit is reached, it would
be nice to inform the app somehow that at least one of the earlier events than
the flushed 10% of pending events has dropped because it has not arrived in
time. This way, the app may have a chance to handle such exception afterwards,
for example, by doing a full scan of the partition to which the dropped event
belongs if possible. We would like to handle such exception for both
CacheContinuousQueryPartitionRecovery.pendingEvts and
CacheContinuousQueryEventBuffer.pending.
> 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)
