Uploaded image for project: 'JBoss Cache'
  1. JBoss Cache
  2. JBCACHE-1527

LockParentForChildInsertRemove ignored with PessimisticLocking

    Details

      Description

      From looking at the JBC 3 code, it seems the
      LockParentForChildInsertRemove configuration is no longer respected for
      pessimistic locking. I can't trace any path from the property in
      Configuration to code that uses it.
      PessimisticLockInterceptor.handlePutCommand, handleMoveCommand and
      handleRemoveNodeCommand all always tell the lock manager to lock
      parents. handleEvictFqnCommand always tells the lock manager not to lock
      parents.

      This is causing failures in buddy replication testing when nodes
      join/leave clusters under load. There's a lot of data gravitation plus
      stuff like migrating defunct backup trees to "DEAD" regions. Too much
      contention for parent level locks.

      Plus locking on the structural parent to add/remove session nodes will
      suck for the session caching use case.

        Gliffy Diagrams

          Attachments

          1. DGTest.java
            3 kB
            Manik Surtani
          2. JBCACHE-1527.patch
            4 kB
            Brian Stansberry

            Issue Links

              Activity

                People

                • Assignee:
                  manik Manik Surtani
                  Reporter:
                  brian.stansberry Brian Stansberry
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: