FYI: we recently pushed a bug fix https://github.com/JanusGraph/janusgraph/pull/2536 which might be related to the problem you encountered. This will be released in 0.6.0.

Marc, thanks for your help. The way you test it is similar to how it works in my environment. I do ConfiguredGraphFactory.open("graph1") as a workaround for the second JanusGraph instance. But the

Hi Anton, I did not feel like debugging your docker-compose file, but I could not find any test covering your scenario on github/janusgraph either, so I just replayed your scenario with the default

Hi Marc, The environment properties in docker-compose are making it work with scylla as a backend storage and with ConfiguredGraphFactory for dynamically created graphs. It works as expected except

After rolling back the PR I mentioned in the beginning of the topic we do not experience any issues. Even back then it was not "out of memory", but the process just ate one full core of CPU and never

After understanding more about the context, I feel https://gist.github.com/mad/df729c6a27a7ed224820cdd27209bade is not a fair comparison between iterator and iterable versions because it assumes all

Hi Anton, If I do a $ docker run janusgraph/janusgraph:latest the logs show it runs with the berkeleyje backend. If I look

Can someone share how you run the benchmark (like what JMH version and what janusgraph version you are using) provided by @mad? I ran the benchmark on master (f19df6) but I see OOM errors for both

I couldn't reproduce this on the v0.4 branch using the below code: @Test public void testTopic81433493() { PropertyKey prop1 = mgmt.makePropertyKey("prop1").dataType(String.class).make();

Hi We use dynamically created graphs in a multi-node JanusGraph cluster. With a single JunusGraph node it seems to work, but when we are using more than one, synchronization between JanusGraph nodes

Hi Adrian, What happens if you rewrite the query to: lmg.traversal().V(analysisVertex).out().emit().repeat( __.in().choose( __.hasLabel("result"),

Hello, I'm having a strange behaviour with janusgraph and I would like to post it here and see if anyone can give me some help. The thing is that I'm doing a tree query for getting my graph data

Hi, You did not answer my questions about the "id" poperty. TinkerPop uses a Token.ID that has the value 'id',

Another really strange observation gremlin>

Have you tried keeping query.batch = true AND query.fast-property = true? Regards, Boxuan

Hi All, Adding these properties in the configuration file affects edge traversal. Retrieving a single edge takes 7 mins of time. 1) Turn on query.batch 2) Turn off query.fast-property Count query is

Hi The issue still persists, and the vertex metadata is still missing for some vertices, after enabling https://docs.janusgraph.org/advanced-topics/eventual-consistency/, has someone seen the same

Opened the issue about this potential bug here: https://github.com/JanusGraph/janusgraph/issues/2524

Hi Fredrick, You are right, this is an issue, so if you want to report this: thanks. Best wishes, Marc

Hi Vinayak, Try below. If it works for you, you can add E2 and D similarly. g.V().has('property1', 'A'). outE().has('property1', 'E').as('e'). inV().has('property1', 'B').