[
https://issues.apache.org/jira/browse/IGNITE-17647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Timonin updated IGNITE-17647:
------------------------------------
Summary: Include in incremental snapshot transactions committed by
TxRecovery (was: Assign ConsistentCutVersion for transaction recovery case)
> Include in incremental snapshot transactions committed by TxRecovery
> --------------------------------------------------------------------
>
> Key: IGNITE-17647
> URL: https://issues.apache.org/jira/browse/IGNITE-17647
> Project: Ignite
> Issue Type: Sub-task
> 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)
