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

Alexey Goncharuk commented on IGNITE-7918:
------------------------------------------

[~aealeksandrov] I am a bit concerned that cleanup is done using a full 
iteration over the {{affMap}}. What is the expected and max size of this map in 
the use-case you were debugging? Do you think it makes sense to change the map 
type to ConcurrentSkipListMap (make AffinityAssignmentKey comparable with 
topVer being compared first)?

> 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
(v7.6.3#76005)

Reply via email to