Nikos, Are these Java-code read or write transactions or Cypher read or write TX that you see the behavior with?
Michael Am 17.03.2014 um 11:31 schrieb Nikos <[email protected]>: > Hello, > I am using Neo4j1.9.5 community edition on a test-drive basis to assess its > performance and gain experience. > I have a graph that is both written to and read from; size is about 10M > nodes, 100M relationships, about 14 Gb. > > In the 1.8 version I was getting a lot of deadlocks, which ended up in > countless restarts, but after moving to 1.9.5 things have been much more > stable, > until recently, that is, where I started getting these BLOCKED threads > problem. > I dug in the code and it seems that all these thread are waiting on the > same instance of org.neo4j.kernel.impl.transaction.TxManager > at org.neo4j.kernel.impl.transaction.TxManager.commit(TxManager.java:344) > > I have seen another forum post about this but there has been no reply. > Any ideas welcome! > > Thanks! > Nk > > > -- > 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. -- 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.
