Pessimistic Force Write Lock doesn't acquire remote lock -------------------------------------------------------- Key: ISPN-3266 URL: https://issues.jboss.org/browse/ISPN-3266 Project: Infinispan Issue Type: Bug Components: Distributed Cache, Locking and Concurrency Affects Versions: 5.3.0.Final Reporter: William Burns Assignee: Pedro Ruivo Fix For: 6.0.0.CR1 Attachments: DistSyncL1PessimisticFuncTest.java Looking into FORCE_WRITE_LOCK it appears it only acquires a local lock in PessimisticLockingInterceptor. Thinking about this, it seems this should acquire only a remote lock on the primary node. Currently this isn't going to block writes at all. I am guessing this was just an oversight when redoing the locking mechanism. This causes other issues such as L1 inconsistencies which is how I ran into this and the locking should only occur on the remote node.