-
Notifications
You must be signed in to change notification settings - Fork 695
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
1.9 FastRouter issues #172
Comments
still beating my head on that :( i was not able to reproduce it, but i have the feeling that it is a very stupid bug (but well hidden) |
It's defiantly rare, I only get 10-100 errors per day and FastRouter is handling few million requests. |
I think it should be fixed. Basically if you get EAGAIN after the first 4 bytes of the uwsgi header the corerouter was calling the header parser again as the hook was not reset. It was a very rare case as it is pretty uncommon to receive only a 4 byte segment from the network stack. |
great, I'll do some testing today to verify it's fixed |
moving from mailing list and jabber so history is in one place, 1.9 FastRouter produces this errors in log:
it's random and it's rare.
With this debug patch:
I'm getting:
The text was updated successfully, but these errors were encountered: