Explanation of error “DeadlockDetectedException: ForsetiClient[0] can’t acquire ExclusiveLock…​ …​”

Under specific scenarios a DeadlockDetectedException may be encountered and the behavior is described at http://neo4j.com/docs/stable/transactions-deadlocks.html. When a DeadlockDetected is encountered one option is to simply retry the statement. As a deadlock detection error is a safe-to-retry error and the user… Read more →

Explore:  


How to diagnose locking issues

Since Neo4j 3.4 it’s possible to better understand locking issues caused by concurrent query. This KB article will not detail the basics of locking in Neo4j. We assume a situation where you concurrently run lots of queries – might be… Read more →

Explore:  


Lock Manager Differences Explained

Work in Progress Community: uses Java intrinsic locks, i.e. ’synchronized’. this might not perform that well on multiprocessor machines uses Thread.sleep() and Thread.interrupt() to wait for locks. this involves context switches which can be expensive keeps global graph or all… Read more →

Explore:  


Shared vs Exclusive Transaction locks

This document describes the meaning of a shared lock as seen by transactions and the difference between a shared and exclusive lock. A “shared lock” means multiple transactions can be holding the same lock at the same time, where “same… Read more →

Explore: