You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by " Kirill Sizov (Jira)" <ji...@apache.org> on 2023/12/26 14:06:00 UTC

[jira] [Updated] (IGNITE-21153) Rethink LockManager extensions

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

 Kirill Sizov updated IGNITE-21153:
-----------------------------------
    Summary: Rethink LockManager extensions  (was: Better LockManager extension)

> Rethink LockManager extensions
> ------------------------------
>
>                 Key: IGNITE-21153
>                 URL: https://issues.apache.org/jira/browse/IGNITE-21153
>             Project: Ignite
>          Issue Type: Task
>            Reporter:  Kirill Sizov
>            Priority: Major
>              Labels: ignite-3
>
> *Motivation*
> There is a {{LockManager}} "extension"  - {{OrphanDetector}} - that checks whether the lock holder is no longer available and fails the waiting transaction.
> So we have a two-way stream of control here - {{LockManager}} notifies {{OrphanDetector}} and expects a response from it.
> Currently {{OrphanDetector}} binds to {{LockManager}} using event notifications, the response from it is handled in an extremely hacky way - using exceptionally completed future.
> *Definition of Done*
> There should be a way to ask {{OrphanDetector}} and handle its response in a more straightforward and synchronous way.



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