[
https://issues.apache.org/jira/browse/IGNITE-26060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18061827#comment-18061827
]
Ignite TC Bot commented on IGNITE-26060:
----------------------------------------
{panel:title=Branch: [pull/12825/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}SPI (Discovery){color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=8897674]]
* IgniteSpiDiscoverySelfTestSuite: TcpDiscoverySpiMBeanTest.testMBean - Test
has low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/12825/head] Base: [master] : New Tests
(16)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Calcite SQL{color} [[tests
16|https://ci2.ignite.apache.org/viewLog.html?buildId=8895699]]
* {color:#013220}IgniteCalciteTestSuite:
TxWithExceptionalInterceptorTest.testTxWithExceptionInterceptor[txCoordRole=PRIMARY,
persistence=true, writeThrough=true] - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
TxWithExceptionalInterceptorTest.testTxWithExceptionInterceptor[txCoordRole=PRIMARY,
persistence=true, writeThrough=false] - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
TxWithExceptionalInterceptorTest.testTxWithExceptionInterceptor[txCoordRole=COORDINATOR_NO_DATA,
persistence=true, writeThrough=true] - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
TxWithExceptionalInterceptorTest.testTxWithExceptionInterceptor[txCoordRole=COORDINATOR_NO_DATA,
persistence=true, writeThrough=false] - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
TxWithExceptionalInterceptorTest.testTxWithExceptionInterceptor[txCoordRole=BACKUP,
persistence=false, writeThrough=true] - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
TxWithExceptionalInterceptorTest.testTxWithExceptionInterceptor[txCoordRole=BACKUP,
persistence=false, writeThrough=false] - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
TxWithExceptionalInterceptorTest.testTxWithExceptionInterceptor[txCoordRole=BACKUP,
persistence=true, writeThrough=true] - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
TxWithExceptionalInterceptorTest.testTxWithExceptionInterceptor[txCoordRole=BACKUP,
persistence=true, writeThrough=false] - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
TxWithExceptionalInterceptorTest.testTxWithExceptionInterceptor[txCoordRole=PRIMARY,
persistence=false, writeThrough=true] - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
TxWithExceptionalInterceptorTest.testTxWithExceptionInterceptor[txCoordRole=PRIMARY,
persistence=false, writeThrough=false] - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
TxWithExceptionalInterceptorTest.testTxWithExceptionInterceptor[txCoordRole=THICK_CLIENT,
persistence=false, writeThrough=true] - PASSED{color}
... and 5 new tests
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=8895784&buildTypeId=IgniteTests24Java8_RunAll]
> 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
> Affects Versions: 2.17
> 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)
