You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vyacheslav Koptilin (Jira)" <ji...@apache.org> on 2024/05/28 10:31:00 UTC

[jira] [Assigned] (IGNITE-22329) Check that cluster is operable after changing the deadlock prevention policy to "Timeout wait"

     [ https://issues.apache.org/jira/browse/IGNITE-22329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vyacheslav Koptilin reassigned IGNITE-22329:
--------------------------------------------

    Assignee: Denis Chudov

> 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)