Date
1 - 2 of 2
Local lock contention on edges
Carlos Cheung <cheung...@...>
So I understand that if I open up separate transactions and modify the schema, a commit on one of the transactions will fail. What I don't understand is why adding edges of the same name between different nodes in different transactions occasionally cause a local lock contention. Sometimes it goes through fine, other times I will encounter an error. A schema has been defined for everything. Strangely I am unable to reproduce this in groovy, but attached is a test case that causes the issue in Python utilizing GremlinClient library. At the bottom is the stack trace from the server when the error occurs.
|
|
Austin Sharp <austins...@...>
My guess would be that it's because you have some kind of index that is being updated when you add those edges (note '
On Monday, March 20, 2017 at 4:25:19 PM UTC-7, Carlos Cheung wrote:
|
|