-
-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Loosing vertex around? #25
Comments
The ArangoDB client has lost the connection to the server (the server closes inactive connections after 300 seconds) Example:
To avoid this you can increase the "keep-alive-timeout" of the server by: |
Thank you, |
Please update blueprints-arangodb-graph to 1.0.15 and try again. (will be available on maven central in some hours) |
ok |
Setting I am trying with a smaller value i.t.
|
I changed the time out handling of the client driver in 1.0.15. So you do not need to change the keep alive timeout of the server anymore. The directory |
No...
BTW there is something strange here: Investigating. |
Sorry for disappearing, but other critical things required my attention. I've good news I was able to make it work with version It required the following actions:
I still have to check if those solutions are enough to process even our bigger sample, but at this point Arango is definitely not Loosing vertex around, so closing now. |
I can not locate a vertex from within gremlin, which I can retrieve in the web GUI:
From the GUI I filter as:
From gremlin I query (searching by attribute wo/key) as:
g.V.has('freebaseid', 68545795554948).next().id
Raised exception:
javax.script.ScriptException: com.tinkerpop.pipes.util.FastNoSuchElementException
Full stack trace: http://pastebin.com/61iPnkBW
Relevant points:
Could someone please help me figuring out what's happening here?
Versions:
ArangoDB: 2.7.7
Gremlin: 2.6.0
blueprints-arangodb-graph: 1.0.14
The text was updated successfully, but these errors were encountered: