Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
SyncWorker.wait() method returns None #983
I am running gunicorn 19.2.0 serving Django 1.7.4 using nginx as a proxy on Centos7.
As a result the worker then dies and then is rebooted by the master. Since I am in a low volume world, this is happening for each worker every timeout seconds (15.0) and really filling my logs.
Is this the expected behaviour? Perhaps this is an artefact of the result of the
My work around is to return an empty list at the end of the
If we provide all the sockets here, it would means we could miss a connection on one of the sockets. Imo a better way would be to returning in the looop if no socket is ready to accept and wait for at least one.
One possible issue by doing this is the thundering herd problem, but that could be handled later. Thoughts?
I'm encountering this problem as well. One side-effect is that clients making http requests to gunicorn occasionally get "socket hang up" errors because there are apparently no free workers to service the request. This isn't a giant problem for me, and doesn't happen very frequently, but it does show that this problem has real-world implications and is not totally benign. I'm eagerly awaiting a new gunicorn release that fixes this.