I would like to know if is safe to use "max-requests" while "thunder-lock" is enabled. Since I started to use "max-requests" I noticed some new messages in the log, saying:
*Fri Jul 06 09:25:26 - [deadlock-detector] a process holding a robust mutex died. recovering...* Fri Jul 06 09:25:26 - ...The work of process 12173 is done. Seeya! Fri Jul 06 09:25:27 - worker 2 killed successfully (pid: 12173) Fri Jul 06 09:25:27 - Respawned uWSGI worker 2 (new pid: 12252) But I have noticed too, that is inconsistent. What I mean is, every time a process hits five requests, the process restarts, but the message of deadlock appear only some times. [uwsgi] master = true die-on-term uid = nginx gid = nginx pidfile = /var/run/uwsgi.pid socket = /tmp/uwsgi.sock stats = /tmp/uwsgi-stats.sock chown-socket = nginx:nginx daemonize = /var/log/uwsgi/n.log log-maxsize = 104857600 log-date = %%a %%b %%d %%H:%%M:%%S log-5xx log-zero log-ioerror = true log-slow = 5000 log-big = 2048 disable-logging chdir = ... module = wsgi cheaper-algo = spare cheaper = 2 cheaper-initial = 2 cheaper-step = 1 cpu-affinity = 1 workers = 4 threads = 5 vacuum = true max-requests = 5 (tests purposes) #enable-threads thunder-lock
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
