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

Posted to issues@ignite.apache.org by "Maksim Timonin (Jira)" <ji...@apache.org> on 2022/09/07 10:24:00 UTC

[jira] [Updated] (IGNITE-17647) Assign ConsistentCutVersion for transaction recovery case

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

Maksim Timonin updated IGNITE-17647:
------------------------------------
    Labels: IEP-89 ise  (was: IEP-89)

> Assign ConsistentCutVersion for transaction recovery case
> ---------------------------------------------------------
>
>                 Key: IGNITE-17647
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17647
>             Project: Ignite
>          Issue Type: New Feature
>            Reporter: Maksim Timonin
>            Assignee: Maksim Timonin
>            Priority: Major
>              Labels: IEP-89, ise
>
> Cut is inconsistent, if a transaction wasn't set with txCutVer. It's possible for transaction recovery cases, when Near node failed and didn't send the Finish message on one or more participated nodes. 
> But relying on transaction recovery protocol it's possible to assign txCutVer from primary, if at least single Finish message was sent.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)