I run a ton of tests against Neo4j community for both basic functionality
and stress testing concurrency behaviour and schema changes. They're all
passing nicely thank you. I thought I'd have a look at how they run against
the enterprise edition and was surprised to experience ~14 failures with
the following representative error message:
org.neo4j.kernel.DeadlockDetectedException: ForsetiClient[42] can't acquire
UpdateLock{objectId=107277620, refCount=1, holder=ForsetiClient[44]} on
SCHEMA(0), because holders of that lock are waiting for ForsetiClient[42].
Wait list:SharedLock[ForsetiClient[44] waits for [42, 44, ], ]
at
org.springframework.data.neo4j.support.query.CypherQueryEngineImpl.query(CypherQueryEngineImpl.java:61)
at
org.springframework.data.neo4j.repository.query.GraphRepositoryQuery.dispatchQuery(GraphRepositoryQuery.java:117)
Are there key differences to the way that locks are managed between the
editions? Secondly, why would the enterprise edition be more likely to
deadlock than community? I didn't notice anything in the documentation that
would lead me to consider it to be a configuration issue.
2.1.3 embedded, SDN.
-Mike
--
You received this message because you are subscribed to the Google Groups
"Neo4j" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
