> Hello. > > I'm trying to make uWSGI gracefully reload its config after I added a > "cron" entry, but I can't seem to do it. I'm using version 2.0.3 and the > Gevent loop engine. > > If I send the master process a SIGHUP signal, it outputs a "Gracefully > killing worker..." but in fact disregards all running greenlets that are > servicing requests, and restarts everything. Requests being serviced are > discarded. This does not happen with "touch-chain-reload", in this case > the workers wait for requests to finish before exiting. > > Is it possible to make uWSGI reload its config, without discarding current > requests or stopping servicing new requests? > > Best regards, > André > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
The gevent loop engine should wait for all running core greenlet (the ones spawned by uWSGI), both when signaling the master and when a single worker shutdown is requested. If i remember correctly you have an https router on front, could it be it is the guilty one ? (there is no graceful reload concept in gateways, and when you reload the master, gateways are destroyed asap) -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
