Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
None
Description
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 JVM crashed due to OOM as GridCacheDistributedQueryFuture.allCol map contains to many entries.
I've put 15kk entries into cache and client failed with OOM after iterating over 10kk entry.
In heapdump I observer 10kk GridCacheDistributedQueryFuture entries.
We have to check if collection cleared correctly and it is really need to collect all entries.
PFA repro.
