I'm thinking harariki was not working as expected though uwsgi was running in single core.
I opened uwsgi logging each request, and I'd like to check if any request processing longer than 20 seconds. If any, then harakiri must be not working properly to kill such processes. On Tue, Oct 23, 2012 at 12:07 AM, Samuel <[email protected]> wrote: > No, I don't think I used async mode, which seems quite difficult to be > handled from the doc. > > I put my django ini here: > > stats = /tmp/uwsgi_statsock >> workers = 40 >> max-requests = 100000 >> listen = 4000 >> socket = :8081 >> chdir = /home/django/envs/product/src/ >> home = ../ >> pythonpath = ./ >> module = django_wsgi >> env = DJANGO_SETTINGS_MODULE=settings >> module = django.core.handlers.wsgi:WSGIHandler() >> daemonize = ./log/uwsgi.log >> logdate = true >> logslow = true >> logbig = true >> log-5xx = true >> disable-logging = true >> master = true >> auto-procname = true >> harakiri = 20 >> harakiri-verbose = true >> single-interpreter = true >> pidfile = ./uwsgi.pid >> touch-reload = ./uwsgi.pid > > > > On Mon, Oct 22, 2012 at 11:55 PM, Roberto De Ioris <[email protected]>wrote: > >> >> Il giorno 22/ott/2012, alle ore 17:50, Samuel <[email protected]> >> ha scritto: >> >> > >> > On Mon, Oct 22, 2012 at 11:37 PM, Roberto De Ioris <[email protected]> >> wrote: >> > >> > >> > nginx has an internal timeout on the response generation (60 seconds by >> default). >> > >> > Maybe you had some response not generating in time (you may want to >> check slow requests in uwsgi logs, to see if some >> > is higher than nginx timeout) >> > >> > i set nginx proxy_read_timeout 120, and I also set harakiri = 20 in >> uwsgi. If any requests waiting longer than 20 seconds, the request itself >> should be killed and the process should be recycled, while nginx cannot >> read timeout connections? >> > >> > -- >> > 吴焱红(Samuel) >> > >> > 博客: blog.shanbay.com >> > >> >> Are you using some kind async/non-blocking mode ? (like the gevent >> plugin). >> >> In such a case, harakiri will be triggered only when ALL of your greenlet >> are blocked. >> >> Per-core soft-harakiri (threads and greenlet cannot be destroyed without >> impacting the whole process, so we can only report >> long-running requests as a log line) will be implemented in 1.4 >> >> -- >> Roberto De Ioris >> http://unbit.it >> JID: [email protected] >> >> _______________________________________________ >> uWSGI mailing list >> [email protected] >> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >> > > > > -- > *吴焱红(Samuel)* > > 博客: blog.shanbay.com > > > > -- *吴焱红(Samuel)* 博客: blog.shanbay.com
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
