You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by "Andrew Mashenkov (JIRA)" <ji...@apache.org> on 2018/11/14 22:26:00 UTC

[jira] [Created] (IGNITE-10263) MVCC: Concurrent cache stop can cause vacuum failure.

Andrew Mashenkov created IGNITE-10263:
-----------------------------------------

             Summary: MVCC: Concurrent cache stop can cause vacuum failure.
                 Key: IGNITE-10263
                 URL: https://issues.apache.org/jira/browse/IGNITE-10263
             Project: Ignite
          Issue Type: Bug
          Components: cache, mvcc
            Reporter: Andrew Mashenkov


The issue can be easily reproduced with IgniteCacheIncrementTxTest in Mvcc mode.

 

Vacuum.cleanup() fails on cctx.gate().enter() if cache is stopped concurrently.

ctx.gate().enter() method fails with IllegalStateException right after readLock has been taken.
So, this lock will be never released and prevent writeLock being taken on node stop.

Replacing enter() with enterIfNotStopped() resolve the issue, but most likely we should release readLock on failure inside gateway.enter().



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