It is possible to overload hackney pool and render it unresponsive or even crash erlang node.
Some process sending simple http requests on a server that can handle not more then N RPS with rate
Process info for a pool shows this:
Pool configuration looks like this:
Since message queue size is huge, pool becomes completely unresponsive.
My proposal: maybe its a good idea to set up some back pressure or introduce some defensive mechanism that will allow to avoid pool lock.
Also it seems a bit unclear when hackney_pool answers
The text was updated successfully, but these errors were encountered:
I'm not sure if it's the same problem but my pools are getting stuck as well. I'm using hackney 1.15.0. Running get stats on the pool returns:
in_use_count is 0 but the queue count is huge.