> Whoa! That's really a nice and elegant solution of deadlock preventions. > Hmm something went wrong. > 1.1-dev-1906 > >
Should be fixed now (both) > Another thing to note: i still think continuing request execution > after usr2 is a bug. It is better to exit(1) in usr2 handler in > worker. I think it is better to make harakiri 2 step: 1) usr2 is sent > to worker and master marks pid as harakiri first step. A worker should > do exit(1) when receives usr2. This will make sleep(1) and kill(kill) > unnessessary in 99% cases. Also removing 1 sec delay in possible lock > deadlock. 2) Master should periodically check for harakiki pids and if > it is in harakiki state for > 1 sec kill(kill) it. Never-less > continuing request handler after usr2 is a bug. > This would require a bit of refactoring as USR2 is not only used by harakiri, but in general i am not against it. -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
