[uWSGI] possible bug? if the first and only request is a websocket request, harakiri is triggered

Igor Katson igor.katson at gmail.com
Sat Apr 5 06:03:21 CEST 2014


Sorry, I forgot to post the answer the day I've written it,

I did not fully understand your response, cause it's about uwsgi
implementation details, but it seems you did confirm the problem, didn't
you?
Do you have any estimates of when 2.1 would be out?

Thanks, Roberto!


On Tue, Mar 11, 2014 at 11:26 AM, Roberto De Ioris <roberto at unbit.it> wrote:

>
> >
> >> Roberto, could you please give a comment on this? Thanks a lot!
> >
> >
> > oops, sorry, completely missed it, i will give a look tomorrow morning
>
>
> first round:
>
> - start request for /index.html
> - set harakiri to 5 seconds
> - start request for /ws
> - re-set harakiri to 5 seconds
> - /index.html ends, harakiri set to 0 (race condition!!!)
> - all continues until the next request is managed...
>
> second round
>
> - start request for /ws (as idnex.html is no more needed)
> - set harakiri to 5 seconds
> - harakiri is now honoured ...
>
>
> Harakiri and multiple cores does not play well, but i am pretty confident
> we can find a solution in 2.1. Some idea ? (maybe it is enough to maintain
> the harakiri per-core instead of per-worker)
>
>
> --
> Roberto De Ioris
> http://unbit.it
> _______________________________________________
> uWSGI mailing list
> uWSGI at lists.unbit.it
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.unbit.it/pipermail/uwsgi/attachments/20140404/720aa970/attachment.html>


More information about the uWSGI mailing list