You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When loading data into the graph I get many of these info logs: 2021-11-12 08:34:28.666 INFO 12322 --- [river-worker-42] o.a.t.gremlin.driver.ConnectionPool : Replace Connection{host=Host{address=localhost/127.0.0.1:8182, hostUri=ws://localhost:8182/gremlin}}, {channel=0595efe9}
When I mean many, i mean 1000s.
Netstat also reveals some interesting results.
Heaps of tcp6 0 0 127.0.0.1:51734 127.0.0.1:8182 TIME_WAIT -
and a few tcp6 0 407 127.0.0.1:54158 127.0.0.1:8182 ESTABLISHED 12322/java
The import would fail until I added janusgraph.storage.cql.request-timeout=10000 to my docker environment.
This did not occur with 0.5.3, is there a configuration option that I could be missing? Or is this a known issue with 0.6.0, although an internet search only mentions the request-timeout issue.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I recently upgraded to Janusgraph 0.6.0
When loading data into the graph I get many of these info logs:
2021-11-12 08:34:28.666 INFO 12322 --- [river-worker-42] o.a.t.gremlin.driver.ConnectionPool : Replace Connection{host=Host{address=localhost/127.0.0.1:8182, hostUri=ws://localhost:8182/gremlin}}, {channel=0595efe9}
When I mean many, i mean 1000s.
Netstat also reveals some interesting results.
Heaps of
tcp6 0 0 127.0.0.1:51734 127.0.0.1:8182 TIME_WAIT -
and a few
tcp6 0 407 127.0.0.1:54158 127.0.0.1:8182 ESTABLISHED 12322/java
The import would fail until I added
janusgraph.storage.cql.request-timeout=10000
to my docker environment.This did not occur with 0.5.3, is there a configuration option that I could be missing? Or is this a known issue with 0.6.0, although an internet search only mentions the request-timeout issue.
Beta Was this translation helpful? Give feedback.
All reactions