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
Match error in hackney_pool:queue_out
#594
Comments
|
@benoitc any debugging pointers? |
|
probably a race condition. i'm investigating |
|
FYI, I was able to create a situation where the errors stopped happening by increasing It also makes me think it might be easier to reproduce by lowering |
|
@benoitc any update on this? I've started to see this issue myself with the default pool in |
|
@alinpopa how/when does it happen? More generally there is a WIP on fixing connection reusing, i will provide a more detailled status tomorrow, should have been earlier but I've been side-tracked. |
|
@benoitc it's a bit difficult to know exactly how it happened, but the only thing I can tell you (from my logs), is that at that time we had a high requests load (again, don't really have numbers to back me up on this), and then it crashed with this: Hope this helps. Thanks. |
|
fixed in cd96ce7 |
I'm seeing a match error for somewhat sporadically... (Elixir stacktrace):
https://github.com/benoitc/hackney/blob/master/src/hackney_pool.erl#L504-L517
It looks like the call to
queue:outon L509 is returning{:empty, _queue}but it's always expecting there to be a valueHackney
1.15.2Erlang/OTP
22.1.3Any ideas what could cause this situation?
The text was updated successfully, but these errors were encountered: