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/01 12:07:00 UTC

[jira] [Updated] (IGNITE-18042) Rework lock management mechanism

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

Denis Chudov updated IGNITE-18042:
----------------------------------
    Summary: Rework lock management mechanism  (was: Rework locks menegment mechanism)

> Rework lock management mechanism
> --------------------------------
>
>                 Key: IGNITE-18042
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18042
>             Project: Ignite
>          Issue Type: Epic
>            Reporter: Vladislav Pyatkov
>            Priority: Major
>              Labels: ignite-3
>
> Today lock management is represented by interface LockManager (implementation into HeapLockManager). This approach has known issue (lock is not token is row id, not possible to replace a mechanism of deadlock prevention and some particular scenarios).
> This epic covers some activity which is connected with work that make the management correctness.



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