Re: [uWSGI] Weirdness with persistent threads

I had a similar issue with ZeroMQ uWSGI and NGINX. What worked for me was turning off uwsgi_buffering and setting uwsgi_read_timeout to 300 on my nginx conf file. On Fri, Apr 7, 2017 at 1:33 PM, Larry Martell wrote: > I have a django app that I serve with nginx and

[uWSGI] Weirdness with persistent threads

I have a django app that I serve with nginx and uwsgi. Some requests that the app receives start python threads that are not complete when the request returns a response to the client. When I run with the django devel server the threads continue to run to completion. But when I run with the djanbo

[uWSGI] post-buffering and read() size

Hello list! Hunting down a rather huge number of syscall peaks on the (FreeBSD) server, I found that uwsgi (2.0.14) issued read() calls with size 1 for data POST-ed from nginx to the uwsgi application. Turned out, I had "post-buffering=1" in the config, remnant from earlier times when I had