You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Scherbakov (Jira)" <ji...@apache.org> on 2021/07/05 14:37:00 UTC

[jira] [Created] (IGNITE-15057) Implement LockManager with deadlock prevention based on operation ordering

Alexey Scherbakov created IGNITE-15057:
------------------------------------------

             Summary: Implement LockManager with deadlock prevention based on operation ordering
                 Key: IGNITE-15057
                 URL: https://issues.apache.org/jira/browse/IGNITE-15057
             Project: Ignite
          Issue Type: Task
    Affects Versions: 3.0.0-alpha2
            Reporter: Alexey Scherbakov
            Assignee: Alexey Scherbakov
             Fix For: 3.0.0-alpha3


We assume two phase locking concurrency control in the first version of tx protocol in Ignite 3.

We need a LockManager implementing this functionality.

If a shared/exclusive lock is acquired in incompatible mode, only "newest" operations are allowed to wait for "oldest", according to ordering based on globally comparable timestamp.

Otherwise, newer transactions are restarted preserving it's timestamp.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)