Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-5654

Make DeadlockDetectingLockManager aware of single-node locking

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 8.0.0.Beta2
    • Fix Version/s: 9.0.0.CR3
    • Component/s: Core
    • Labels:
      None

      Description

      DeadlockDetectingLockManager seems to assume that the node that started a transaction acquires a local lock before replicating, which is wrong since we switched to locking only on the primary owner.

      In particular, isSameKeyDeadlock can probably be removed altogether.

        Attachments

          Activity

            People

            Assignee:
            dberinde@redhat.com Dan Berindei
            Reporter:
            dberinde@redhat.com Dan Berindei
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: