[ 
https://issues.apache.org/jira/browse/IGNITE-8892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16550677#comment-16550677
 ] 

ASF GitHub Bot commented on IGNITE-8892:
----------------------------------------

GitHub user zstan opened a pull request:

    https://github.com/apache/ignite/pull/4391

    IGNITE-8892 add additional test.

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-8892-zstan

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/4391.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4391
    
----
commit 36f743f739e34fada7db2826827e1aea1136b7a8
Author: Andrey V. Mashenkov <andrey.mashenkov@...>
Date:   2018-06-28T14:45:06Z

    ignite-8892: Get rid of CacheQuery.keepAll flag.

commit 0ffd92dac85f5a7e75a1902b2b20ff643b058b4a
Author: Evgeny Stanilovskiy <estanilovskiy@...>
Date:   2018-07-20T09:33:46Z

    IGNITE-8892 add additional test.

----


> 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)

Reply via email to