[
https://issues.apache.org/jira/browse/IGNITE-17647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Timonin updated IGNITE-17647:
------------------------------------
Description:
Currently IS is considered inconsistent if any checked transction committed
during TxRecovery mechanism.
But there are cases when it's possisble to find whether tx should be included
to IS or not:
# Transaction on nodes are PREPARED
# Every node adds the transaction to await list
# Originated node (client) fails.
# Nodes starts communicate with each other to find transaction status. During
this communication it's possible to make a decision.
was:
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.
> 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
>
> Currently IS is considered inconsistent if any checked transction committed
> during TxRecovery mechanism.
> But there are cases when it's possisble to find whether tx should be included
> to IS or not:
> # Transaction on nodes are PREPARED
> # Every node adds the transaction to await list
> # Originated node (client) fails.
> # Nodes starts communicate with each other to find transaction status.
> During this communication it's possible to make a decision.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
