We have N process of a wsgi app running behind nginx acting as a 
proxy. When we release an update, we either have to restart each item 
individually or issue a `restart wsgiapp:*` command. The problem with 
the latter is that it stops all the processes, *then* starts them all. 
This causes some requests to the app to fail. What would be useful would 
be to stop/start each process individually, so requests can continue to 
be served (nginx will simply fail over to the next backend when one 
doesn't respond) and will allow us to keep a reasonable "uptime".
_______________________________________________
Supervisor-users mailing list
Supervisor-users@lists.supervisord.org
http://lists.supervisord.org/mailman/listinfo/supervisor-users

Reply via email to