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

Jurijs Grabovskis commented on IGNITE-12350:
--------------------------------------------

Any updates here?

Got similar problem in 2.7.6 release. atomicityMode is unset or set 
TRANSACTIONAL (for most caches). There are some Ignite server nodes and a lot 
of clients (10+). After some time and under load client nodes got OOM errors 
and then restarted + reconnected to cluster, therefore leading to topology 
update and growing of MvccProcessorImpl.recoveryBallotBoxes , which leads to 
other client nodes to crash because of OOM and so on like a snowball.

Will try to attach screenshots from MemoryAnalyzer tool.

Are there any possibilities at least of safe workaround? !proxy-memory-leak.png!

> MVCC activated and causing memory leak (OOM) despite no mvccEnabled caches
> --------------------------------------------------------------------------
>
>                 Key: IGNITE-12350
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12350
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.7.5
>            Reporter: Ming Vuong
>            Priority: Major
>         Attachments: MATheap.jpg, proxy-memory-leak.png, proxy-oom-2.png
>
>
> We have a critical memory leak where mvccCoordinator is still selected and 
> mvcc is still 'activated' despite having no mvccEnabled caches, this is 
> causing constant OOM crashes and issues on both server and client nodes.
> All client CacheAtomicityModes are of type ATOMIC, and for server config 
> persistence is false, TCPDiscoverySpi used and PeerClassLoadingEnabled=true.
> There are two server JVM instances on two separate nodes. One of the servers 
> consistently get an OOM error, as well as all clients, due to the same 
> recoveryBallotBoxes HashMap constantly increasing in size and unable to be 
> Garbage Collected.
> Attached is Eclipse Memory Analyzer Tool screenshot on the heap dump close to 
> one of the server JVM OOM crashes. The same heap analysis result is apparent 
> for all clients as well.
> !MATheap.jpg!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to