On Sat March 9 2013 16:28:01 Roberto De Ioris wrote: > Ok, now it is more clear, basically you are hitting a race condition with > the old vassals still shutting down and the new one of the new master > copy. > > With tcp socket is not a problem because the second vassal will simply > fail until the old one dies. With UNIX socket you could have problems > because the new instance overwrite the old socket, and if you have vacuum > in place the old one will delete it as soon as it end (yeah, this is a > real mess). > > For such a case i suggest the use of the flock/flock-wait options. That > options force instances to lock a file on startup avoding copies to spawn > until the lock is released.
I've added: flock = %p to the vassal config file and it seems to be working now. Even if I use both --master and --emperor options. I didn't see anything saying that I needed to use both flock and flock-wait so I assume I don't. In any event, the vassals are reloading correctly now. There still seems to be a small amount of time where a request won't be served, but that is most likely due to what you mentioned before about the difference between nginx and uwsgi. Thank you for all your help. I look forward to that feature making it's way into the project. Bjorn
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
