[
https://issues.apache.org/jira/browse/IGNITE-5935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16633377#comment-16633377
]
Ivan Pavlukhin edited comment on IGNITE-5935 at 10/1/18 8:24 AM:
-----------------------------------------------------------------
We should support recovery in slightly different scenarios depending on
following:
* Is failed node server?
* Is failed node mvcc coordinator?
Also attention should be put on backup transaction rollback.
Q: Who should be an initiator of rollback procedure on backup?
A: Primary (DhtLocal) TX rolls back dependent backup TXs (DhtRemote).
was (Author: pavlukhin):
We should support recovery in slightly different scenarios depending on
following:
* Is failed node server?
* Is failed node mvcc coordinator?
Also attention should be put on backup transaction rollback. It is not
currently clear who should be an initiator of rollback procedure on backup.
> 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.
> Also recovered transaction should be removed from active transactions list on
> mvcc coordinator.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
