Replies: 5 comments 2 replies
-
And there are even more problems. Running the exact same code (again in parallel) sometimes generates this:
The exception is raised at dropping the vertices. The vertices to drop are selected using a mixed index:
Where However, the set of vertices each thread drops are / should be totally separate and not overlap. |
Beta Was this translation helpful? Give feedback.
-
Thanks for reporting. Can you please add the following details:
|
Beta Was this translation helpful? Give feedback.
-
Thanks alot for the answer.
EDIT: Output of printSchema would be very verbose, but it is quite simple: All vertex properties have cardinality As for the problem here, the Another thing I encountered with
This also went away when switching to the default lock-mode. To conclude, I suspect a thread safety issue for dropping vertices and adding properties in case of |
Beta Was this translation helpful? Give feedback.
-
Berkeleyje lockmodes are documented here.
|
Beta Was this translation helpful? Give feedback.
-
I am afraid, we now also encountered the |
Beta Was this translation helpful? Give feedback.
-
Using Janusgraph 0.6.1 (org.janusgraph:janusgraph-berkeleyje:0.6.1) with JRuby and Lucene index (though I guess this is not a mixed index problem). This is the config we are using:
We open a threaded transaction:
Then each thread drops some vertices and afterwards creates new vertices and adds properties to those vertices:
After all threads are done dbtx is committed. The
.property
gremlin calls (or the.iterate
calls, sorry not sure atm) sometimes (not deterministically) fail with such stacktrace:The graph does have composite and mixed indices, but non of the composite indices are unique. When adding the properties and vertices sequentially and not hitting the transaction in parallel, we did not encounter this problem. Only when doing this in parallel. Also, the property key
~T$SchemaName
seems to be something JanusGraph internal, so I suspect a bug here. Should I open a bug report? I probably won't be able to boil down the problem any further.Also, might this be related to #3205 ?
best
Beta Was this translation helpful? Give feedback.
All reactions