[
https://issues.apache.org/jira/browse/IGNITE-18043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17652419#comment-17652419
]
Vladislav Pyatkov commented on IGNITE-18043:
--------------------------------------------
Merged 3ac9af1090976b5588944820caa33a9118b10432
> 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
> Time Spent: 20m
> Remaining Estimate: 0h
>
> *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)
