ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan Pavlukhin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-5935) MVCC TX: Tx recovery protocol
Date Tue, 25 Sep 2018 13:12:00 GMT

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

Ivan Pavlukhin updated IGNITE-5935:
-----------------------------------
    Description: 
Transaction recovery procedure is initiated when near node failed before transaction was finished.
In MVCC transactions _partition update counter_ modification is started on prepare phase.
If a transaction was prepared at least on one node we need to finish _partition update counter_
modification consistently on all participating nodes.

  was:
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.


> 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: Ivan Pavlukhin
>            Priority: Major
>             Fix For: 2.7
>
>
> Transaction recovery procedure is initiated when near node failed before transaction
was finished.
> In MVCC transactions _partition update counter_ modification is started on prepare phase.
If a transaction was prepared at least on one node we need to finish _partition update counter_
modification consistently on all participating nodes.



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

Mime
View raw message