[
https://issues.apache.org/jira/browse/IGNITE-26060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeny Stanilovsky reassigned IGNITE-26060:
-------------------------------------------
Assignee: Evgeny Stanilovsky
> FailureHandler isn't called on TX coordinator node in certain scenarios
> -----------------------------------------------------------------------
>
> Key: IGNITE-26060
> URL: https://issues.apache.org/jira/browse/IGNITE-26060
> Project: Ignite
> Issue Type: Bug
> Reporter: Sergey Chugunov
> Assignee: Evgeny Stanilovsky
> Priority: Major
>
> Tests implemented for IGNITE-25641 have shown that a server node acting as a
> TX coordinator may not be failed by FailureHandler (FH) when the following
> conditions are met:
> # The node hosts a primary or backup partition involved into the transaction.
> # An error occurred during commit phase of the transaction on that node..
> At the same time "regular" primary or backup nodes that don't serve as TX
> coordinators correctly call FH and take proper actions.
> It looks like that leaving the node alive and not calling FH in this
> situation may lead to a data integrity violation when the same keys may have
> different values on different nodes.
> We need to fix this carefully to avoid calling FH on nodes that act like TX
> coordinators but don't store any data related to that transaction (e.g. if a
> transaction started for some reason on an empty server node or it was a thick
> client node coordinating the tx).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
