Thanks, Roberto! Adding --master-fifo and echoing “r” to it does the trick.
I wonder if it’s worth adding a note to the signals page to see the master-fifo page for graceful shutdowns? I didn’t understand the significance of the Master Fifo sentence at the bottom of the http://uwsgi-docs.readthedocs.org/en/latest/Management.html page. -Jeff On Aug 10, 2014, at 12:05 AM, Roberto De Ioris <[email protected]> wrote: > >> >> Hi Uwsgi List, >> >> Is there a way to gracefully stop uwsgi? As in: stop accepting new >> requests, but finish any existing in-flight requests. >> >> I see an option for a graceful reload, but that won’t work for our >> situation. Both SIGTERM and SIGINT are instant stops; any in-process >> requests get a 503 response generated (at least, that’s what I’m seeing in >> our setup). Running another process in front of uwsgi is not a good >> solution for us either — we already have varnish talking to our backend >> nodes. >> >> Thanks! >> >> -Jeff >> _______________________________________________ >> uWSGI mailing list >> [email protected] >> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >> > > > http://uwsgi-docs.readthedocs.org/en/latest/MasterFIFO.html > > -- > Roberto De Ioris > http://unbit.it > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
