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

Posted to issues@ignite.apache.org by "Andrew Mashenkov (JIRA)" <ji...@apache.org> on 2018/11/15 07:57:00 UTC

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

     [ https://issues.apache.org/jira/browse/IGNITE-10263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Mashenkov reassigned IGNITE-10263:
-----------------------------------------

    Assignee: Andrew Mashenkov

> 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
>            Assignee: Andrew Mashenkov
>            Priority: Blocker
>              Labels: Hanging
>             Fix For: 2.7
>
>
> 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() resolves 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)