[IGNITE-11152] IgniteTxManager.idMap possible memory leak

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8
• Component/s: mvcc
• Labels: memory-leak mvcc_stability transactions
• Assignee: Roman Kondakov
• Reporter: Stepachev Maksim
• Created: 30/Jan/19 16:00
• Updated: 10/Apr/19 12:44
• Resolved: 07/Mar/19 11:18

Description

CacheContinuousQueryAsyncFailoverMvccTxSelfTest.testMultiThreadedFailover sometimes finished with OMM.

Heapdump analyze showed that leak happened in IgniteTxManager.idMap, this map contains 2_097_152 instances of GridNearTxLocal with ACTIVE state and without finishFut and prepFut.

 

while (!updated) {
 try {
 prevVal = (Integer)qryClnCache.getAndPut(key, val);
updated = true;
 }
 catch (CacheException e) {
 assertSame(atomicityMode(), CacheAtomicityMode.TRANSACTIONAL_SNAPSHOT);
 }
 }

 

 

Possible the CacheException is common and may hide wrong cases. Change it at specific (ignite-10976).  

Issue Links

• blocks: IGNITE-11124 CacheContinuousQueryAsyncFailoverMvccTxSelfTest::testMultiThreadedFailover sometimes throwing oom
• duplicates: IGNITE-11124 CacheContinuousQueryAsyncFailoverMvccTxSelfTest::testMultiThreadedFailover sometimes throwing oom
• is blocked by: IGNITE-10976 MVCC: Sql API methods should throw proper TransactionExceptions in case of tx failure.
• links to: GitHub Pull Request #6220
• links to: TC run