[
https://issues.apache.org/jira/browse/IGNITE-22329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17850464#comment-17850464
]
Denis Chudov commented on IGNITE-22329:
---------------------------------------
This change caused only failure of 17 policy-specific tests.
> Check that cluster is operable after changing the deadlock prevention policy
> to "Timeout wait"
> ----------------------------------------------------------------------------------------------
>
> Key: IGNITE-22329
> URL: https://issues.apache.org/jira/browse/IGNITE-22329
> Project: Ignite
> Issue Type: Task
> Reporter: Denis Chudov
> Assignee: Denis Chudov
> Priority: Major
> Labels: ignite-3
>
> *Motivation*
> "Timeout wait" deadlock prevention policy (see
> org.apache.ignite.internal.tx.TimeoutDeadlockPreventionTest ) is different
> from WaitDie that is default. Before any benchmarking, we should check that
> changing the policy would not lead to inoperability of the transactions
> engine (multiple TC failures beside the specific tx tests checking the
> deadlock prevention).
> *Definition of done*
> * change the deadlock prevention policy (no other way from hardcode it)
> * check the teamcity tests after it
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
