You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Vladislav Pyatkov (Jira)" <ji...@apache.org> on 2022/11/01 12:55:00 UTC

[jira] [Created] (IGNITE-18043) Replaceable deadlock prevention mechanism

Vladislav Pyatkov created IGNITE-18043:
------------------------------------------

             Summary: Replaceable deadlock prevention mechanism
                 Key: IGNITE-18043
                 URL: https://issues.apache.org/jira/browse/IGNITE-18043
             Project: Ignite
          Issue Type: Improvement
            Reporter: Vladislav Pyatkov


We have an embedded deadlock prevention strategy (presently, it is _Wait-Die_). Although, 
[the original paper|https://people.eecs.berkeley.edu/~brewer/cs262/concurrency-distributed-databases.pdf] about deadlock prevention contains another two strategies: _priorities_ and _Wound-Wait_. Also, the mechanism should give a possibility to not use any strategy to prevent deadlock.
All told, above shows we need to separate the prevention strategy in dedicate interface (which even has one implementation _Wait-Die_).  Another implementation will be released by necessary.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)