Denis Chudov created IGNITE-19800:
-------------------------------------
Summary: Define the scope of work required for changing the
default deadlock prevention policy
Key: IGNITE-19800
URL: https://issues.apache.org/jira/browse/IGNITE-19800
Project: Ignite
Issue Type: Task
Reporter: Denis Chudov
*Motivation*
There is {{org.apache.ignite.internal.tx.DeadlockPreventionPolicy}} interface
and it's default implementation used in Ignite 3 -
{{{}org.apache.ignite.internal.tx.impl.WaitDieDeadlockPreventionPolicy{}}}.
There are also tests creating other implementations of this interface (no-wait,
timeout-wait, etc.) but they actually check the ability of HeapLockManager to
work with these different policies. The consequences of switching Ignite to
another default policy are unknown - most likely there will be many failing
tests, including integration ones.
We should create a branch with another default deadlock prevention policy and
run all tests on it, to define a scope of work that will be required if we
decide to switch the default.
*Definition of done*
The scope of work related to switch of the default deadlock prevention policy
is known.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
