[ https://issues.apache.org/jira/browse/IGNITE-8892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16534850#comment-16534850 ]
Eduard Shangareev commented on IGNITE-8892: ------------------------------------------- Hi, guys. I don't see any new tests. Is it impossible to add new one which would check no OOM? > 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 > Assignee: Andrew Mashenkov > Priority: Critical > Labels: OutOfMemoryError > 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 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. -- This message was sent by Atlassian JIRA (v7.6.3#76005)