You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/04/09 13:37:00 UTC
[jira] [Commented] (IGNITE-7918) Huge memory leak when data
streamer used together with local cache
[ https://issues.apache.org/jira/browse/IGNITE-7918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16430534#comment-16430534 ]
ASF GitHub Bot commented on IGNITE-7918:
----------------------------------------
GitHub user aealeksandrov opened a pull request:
https://github.com/apache/ignite/pull/3778
IGNITE-7918: memory leak was fixed. Unit test was added.
Some caches didn't take into account that topology minor version could be changed during creating/destroying of the caches dynamically. These places were fixed.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7918
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3778.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 #3778
----
commit 15b8623c684c6250c1c700459299e7986fdd566f
Author: Andrei Aleksandrov <ae...@...>
Date: 2018-04-09T13:32:45Z
IGNITE-7918: memory leak was fixed. Unit test was added.
----
> Huge memory leak when data streamer used together with local cache
> ------------------------------------------------------------------
>
> Key: IGNITE-7918
> URL: https://issues.apache.org/jira/browse/IGNITE-7918
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.3
> Reporter: Zbyszek B
> Assignee: Andrey Aleksandrov
> Priority: Blocker
> Fix For: 2.5
>
> Attachments: Demo.java, MemLeak-Ignite.png, MemLeak-Ignite.txt
>
>
> Dear Igniters,
> We observe huge memory leak when data streamer used together with local cache.
> In the attached demo producer produces local cache with single binary object and passes this to the queue. Consumer picks up the cache from the queue, constructs different binary object from it, adds it to global partitioned cache and destroys local cache.
> This design causes a significant leak - the whole heap is used within minutes (no matter if this is 4G or 24G).
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)