Closed yoelfme closed 6 years ago
Hi @yoelfme,
The 500 error, is returned by the controller, as a result of the timeout you see above.
That timeout error is happening because the db_connection is trying to checkout a new socket, but it can only wait 5_000
(5 seconds!), after this the call exits. It could be the connection is blocking trying to handshake with the db? Do you monitor the db? If yes, maybe you noticed any anomalies? I'd reluctantly suggest to increase the :pool_timeout
option in the config, to 7_000
let's say?! But this will only put more pressure on the pool if the db/network/etc is at fault?! Also increasing the pool size may help, if you have lots of requests (per second). I'd start with the latter.
However, you didn't specify the OTP version?! It could be that you're experiencing this: db_connection/issues/127??
Let me know how it goes, but I believe it a slow handshake at play, unless the issue above.
Hello, in the latest weeks I was working in a project using Bolt Sips to connect to Neo4j, and today I deployed my service to production but I'm experience some issues, I'm receiving a lot of requests and doing almost 5 queries to Neo4j per request, but sometimes that queries give me a timeout and then my requests answer with an 500 status code.
This is the error:
Environment:
And my bolt sips configuration is:
My application supervisor has this childrens
It would be great to get your feedback about this issue.
Thanks for your help