Unable to lock store directory: [path] – Neo4j storage subsystem lock acquisition behavior
Goal: Clarify whether Neo4j’s storage layer should automatically retry obtaining an exclusive lock on its data directory when a transient NFS latency causes the initial lock attempt to fail, or whether it should treat the failure as fatal and shut down immediately. Constraints: The behavior varies between Neo4j 3.x, 4.x, and 5.x releases and can be influence
neo4j