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
