ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Goncharuk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-7918) Huge memory leak when data streamer used together with local cache
Date Mon, 16 Apr 2018 14:09:00 GMT

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

Alexey Goncharuk commented on IGNITE-7918:

[~aealeksandrov], in your updated implementation {{compareTo}} is not consistent with {{equals}},
so it looks like in affinity history map will always be only one entry per topology version.

> 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: Major
>             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

View raw message