[ https://issues.apache.org/jira/browse/IGNITE-6962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexei Scherbakov reassigned IGNITE-6962: ----------------------------------------- Assignee: Alexei Scherbakov > Reduce ExchangeHistory memory consumption > ----------------------------------------- > > Key: IGNITE-6962 > URL: https://issues.apache.org/jira/browse/IGNITE-6962 > Project: Ignite > Issue Type: Bug > Affects Versions: 2.1 > Reporter: Alexander Belyak > Assignee: Alexei Scherbakov > Attachments: histo18175_s1.txt, leak.jpg > > > GridDhtPartitionExchangeManager$ExhcangeFutureSet store huge message > GridDhtPartitionsFullMessage with IgniteDhtPartitionCountersMap2 for each > cache group with two long[partCount]. If we have big grid (100+ nodes) with > large amount of cacheGroups and partitions in > CachePartitionFullCountersMap(long[] initialUpdCntrs; long[] updCntrs;) > <cacheGroups>*<2 arrays>*<partCount>*<sizeOflong=8> = > GridDhtPartitionsFullMessage size and we store 1000 of messages in history. > To reproduce: start few cacheGroup with huge number of partitions with few > caches and analyze heap dump in Eclipse MAT (for example) -- This message was sent by Atlassian JIRA (v6.4.14#64029)