uWSGI request timeout in Python

Question

Trying to set the timeout for requests in uWSGI, I'm not sure of the correct setting. There seem to be multiple timeout options (socket, interface, etc.) and it's not readily evident which setting to configure or where to set it.

The behavior I'm looking for is to extend the time a request to the resource layer of a REST application can take.

Tombart · Accepted Answer · 2014-09-02T22:02:11.537

90

You're propably looking for the harakiri parameter - if request takes longer than specified harakiri time (in seconds), the request will be dropped and the corresponding worker recycled.

For standalone uwsgi (ini config):

[uwsgi]
http = 0.0.0.0:80
harakiri = 30
...

If you have nginx proxy before uwsgi you have to increase timeout as well:

  location / {
    proxy_pass http://my_uwsgi_upstream;
    proxy_read_timeout 30s;
    proxy_send_timeout 30s;
  }

If you want (for some strange reason) higher timeout than 60s, you might consider communication over uwsgi protocol. Configuration is quite similar nginx site:

location / {
    uwsgi_read_timeout 120s;
    uwsgi_send_timeout 120s;
    uwsgi_pass  my_upstream;
    include     uwsgi_params;
}

uwsgi:

[uwsgi]
socket = 0.0.0.0:80
protocol = uwsgi
harakiri = 120
...

edited Sep 02 '14 at 22:02

answered Aug 29 '14 at 17:32

Tombart

30,520
16
123
136

I used the uwsgi protocol option and it works. Thanks. – lukik Aug 04 '15 at 02:57
1

Some queries or operations can easily take longer than 60s. Why would it be considered strange? – AlxVallejo Jun 05 '19 at 20:16
Because most users won't want to wait >60 seconds. And don't try to explain why you don't have a choice, I know. – Camusensei Jul 25 '19 at 10:16
I get error `NameError: name 'uwsgi' is not defined` – Harry Moreno Oct 20 '20 at 17:31
turns out I was adding that to a file for systemd config, not the .ini for flask – Harry Moreno Oct 20 '20 at 18:42
1

Super! I changed `uwsgi_read_timeout` and `uwsgi_send_timeout`. And it works for me! – Rufat May 05 '23 at 07:11

score 24 · Answer 2 · answered Feb 11 '15 at 15:44

24

Setting http-timeout worked for me. I have http = :8080, so I assume if you use file system socket, you have to use socket-timeout.

answered Feb 11 '15 at 15:44

iurii

2,597
22
25

1

I was able to extend the timeout by only using the `http-timeout` parameter in the uwsgi config. I didn't need `--harakiri`. (and I also needed to set `proxy_read_timeout` and `proxy_send_timeout` in the nginx config as @Tombart said above) – nttaylor Aug 10 '17 at 17:09
will there be any issues if I used both ? I'm running into https://stackoverflow.com/questions/67407446/oserror-write-error-python-flask-sigpipe-writing-to-a-closed-pipe-socket-fd – DJ_Stuffy_K May 05 '21 at 20:08
In my case running `uwsgi` directly it was also the `--http-timeout` parameter. – white_gecko May 07 '21 at 18:04

score -2 · Answer 3 · edited Aug 07 '21 at 12:06

-2

it worked for me by comment #master = true and put this, lazy-apps = true

in uwsgi.ini file

edited Aug 07 '21 at 12:06

Muhammmed Nihad

161
1
1
12

answered Apr 17 '21 at 05:31

Shahram

27
4

uWSGI request timeout in Python

3 Answers3

Linked