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

Ignite TC Bot commented on IGNITE-12350:
----------------------------------------

{panel:title=Branch: [pull/8152/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8152/head] Base: [master] : New Tests 
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}MVCC Cache{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=5538631]]
* {color:#013220}IgniteCacheMvccTestSuite: 
MvccStructuresOverheadTest.testWithoutMvcc - PASSED{color}
* {color:#013220}IgniteCacheMvccTestSuite: 
MvccStructuresOverheadTest.testWithMvcc - PASSED{color}

{panel}
[TeamCity *--> Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5538704&buildTypeId=IgniteTests24Java8_RunAll]

> 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
>            Assignee: Vladislav Pyatkov
>            Priority: Major
>         Attachments: MATheap.jpg, proxy-memory-leak.png, proxy-oom-2.png
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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