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

Posted to issues@ignite.apache.org by "Igor Seliverstov (JIRA)" <ji...@apache.org> on 2018/08/17 11:12:00 UTC

[jira] [Commented] (IGNITE-5935) MVCC TX: Tx recovery protocol

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

Igor Seliverstov commented on IGNITE-5935:
------------------------------------------

Since Cache API internals are going to be rethought and reworked it makes sense to suspend the task and return to it after IGNITE-7764 is done.

> MVCC TX: Tx recovery protocol
> -----------------------------
>
>                 Key: IGNITE-5935
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5935
>             Project: Ignite
>          Issue Type: Task
>          Components: cache, mvcc
>            Reporter: Semen Boikov
>            Assignee: Igor Seliverstov
>            Priority: Major
>             Fix For: 2.7
>
>
> Tx recovery doesn't work properly for txs over MVCC enabled caches using Cache API. It requires MvccSnapshot which may not be acquired at recovery time.
> Need to implement logic for checking whether snapshot was already gotten by one of tx participants and use existing one, request and spread between participants a new snapshot otherwise.



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