You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Denis Chudov (Jira)" <ji...@apache.org> on 2022/11/15 08:10:00 UTC

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

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

Denis Chudov reassigned IGNITE-18043:
-------------------------------------

    Assignee: Denis Chudov

> Replaceable deadlock prevention mechanism
> -----------------------------------------
>
>                 Key: IGNITE-18043
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18043
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vladislav Pyatkov
>            Assignee: Denis Chudov
>            Priority: Major
>              Labels: ignite-3
>
> *Motivation:*
> We have an embedded deadlock prevention strategy (presently, it is _Wait-Die_). Although, [the original paper|https://dl.acm.org/doi/pdf/10.1145/320251.320260] 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.
> *Definition of Done:*
> A deadlock resolution strategy (_ResolutionStrategy_) has to be extracted to interface, which parametrizes _LockManager_. Wait-Die strategy (_WaitDieLockResolutionStrategy_) will be the only one implementation of _ResolutionStrategy_.
> _HeapLockManager_ should be parametrized by _WaitDieLockResolutionStrategy_.



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