Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-15057

Implement LockManager with deadlock prevention based on operation ordering

    XMLWordPrintableJSON

Details

    • Task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 3.0.0-alpha2
    • 3.0.0-alpha3
    • None

    Description

      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.

      More specifically, suppose a transaction Ti tries to wait for Tj => lock order is [Tj, Ti]. If Ti has lower priority than Tj (i.e., Ti is younger than Tj), then Ti is permitted to wait => [Tj=10, Ti=20]. Otherwise [Tj=20, Ti=10] => Ti is aborted.

      Aborted transactions must be restarted preserving it's timestamp.

      Attachments

        Issue Links

          Activity

            People

              ascherbakov Alexey Scherbakov
              ascherbakov Alexey Scherbakov
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 50m
                  50m