ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Kondakov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-11152) IgniteTxManager.idMap possible memory leak
Date Wed, 06 Mar 2019 15:46:00 GMT

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

Roman Kondakov commented on IGNITE-11152:
-----------------------------------------

[~amashenkov], {{IgniteTxHeuristicCheckedException}} is thrown on Dht and Remote nodes after
the near transaction is already committed, so there is no need to cleanup tx manager after
this exception.

{{IgniteInterruptedCheckedException}} is thrown when tx is waiting on {{get()}} method of
{{NearEnlistFuture}} or chained {{PostLock}} future. So if this waiting is interrupted, anyway
we have a finish future which will cleanup tx manager on it's finish.

> IgniteTxManager.idMap possible memory leak
> ------------------------------------------
>
>                 Key: IGNITE-11152
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11152
>             Project: Ignite
>          Issue Type: Bug
>          Components: mvcc
>            Reporter: Stepachev Maksim
>            Assignee: Roman Kondakov
>            Priority: Major
>              Labels: memory-leak, mvcc_stabilization_stage_1, transactions
>             Fix For: 2.8
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> 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.*
>  
> {code:java}
> while (!updated) {
>  try {
>  prevVal = (Integer)qryClnCache.getAndPut(key, val);
> updated = true;
>  }
>  catch (CacheException e) {
>  assertSame(atomicityMode(), CacheAtomicityMode.TRANSACTIONAL_SNAPSHOT);
>  }
>  }
> {code}
>  
>  
> Possible the CacheException is common and may hide wrong cases. Change it at specific
(ignite-10976).  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message