[jira] [Created] (IGNITE-8892) Iterating over large dataset via ScanQuery can fails with OOME.

["Andrew Mashenkov (JIRA)" <ji...@apache.org>]

Andrew Mashenkov created IGNITE-8892:
----------------------------------------

             Summary: Iterating over large dataset via ScanQuery can fails with OOME.
                 Key: IGNITE-8892
                 URL: https://issues.apache.org/jira/browse/IGNITE-8892
             Project: Ignite
          Issue Type: Bug
          Components: cache
            Reporter: Andrew Mashenkov
             Fix For: 2.7
         Attachments: ScanQueryOOM.java

Seems, iterating over query iterator (ScanQuery at least, but may be other affected as well) on client node cause memory leakage.

The use case is quite simple.
Start server and client. Put much data into cache, then iterate over all entries via ScanQuery.
Looks like Ignite fails with OOM due GridCacheDistributedQueryManager.futs map contains to many GridCacheDistributedQueryFuture futures.



I've put 15kk entries into cache and client failed with OOM after iterating over 10kk entry.
In heapdump I observer 2*10^9 GridCacheDistributedQueryFuture futures. 

We have to check
 # if these futures removed from map correctly.
 # we don't create unnecessary futures.

PFA repro.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)