Concurrent requests to JanusGraphServer- Exception: Failed to authenticate
, when connection pool size is >1
#4181
Unanswered
devcode100
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi All,
I am facing issue when trying to load test with concurrent requests to gremlin server of JanusGraph.
Backend: cassandra
Single node set up.
The
GraphTraversalSource
object is created once and used across the application.When tried to load test(using default gremlin driver Cluster settings for connection pool (min 2 , max 8)) starting with 100req/sec, getting below error and around 80% requests failed.
Error: org.apache.tinkerpop.gremlin.driver.exception.ResponseException: Failed to authenticate
The simple logic : g.V().hasLabel("god").count() is been run in the request
Seems like a Gremlin issue or is there any configuration tuning to be made?
The only way I could solve this was by increasing the connection pool closer to concurrent requests, but may not be the ideal approach for a throughput for 1K req/sec(optimistic)
If the connection pool is set to (min 1 , max 1) all requests succeeds without authentication issue, when connection pool > 1 then the failed to authenticate issue occurs.
How can I effectively scale the concurrent requests in JanusGraph?
It will be great if I get recommendations for a production rollout.
Requesting your insights
Beta Was this translation helpful? Give feedback.
All reactions