[prev in list] [next in list] [prev in thread] [next in thread] 

List:       uwsgi
Subject:    [uWSGI] possible bug? if the first and only request is a websocket request, harakiri is triggered
From:       roberto () unbit ! it (Roberto De Ioris)
Date:       2014-03-11 18:26:50
Message-ID: 0835fec6515d4d4c1c01b06e4e827971.squirrel () manage ! unbit ! it
[Download RAW message or body]


>
>> 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

[prev in list] [next in list] [prev in thread] [next in thread]