NGINX: upstream timed out (110: Connection timed out) while reading response header from upstream

后端 未结 11 1914
余生分开走
余生分开走 2020-11-28 19:47

I have Puma running as the upstream app server and Riak as my background db cluster. When I send a request that map-reduces a chunk of data for about 25K users and returns i

11条回答
  •  佛祖请我去吃肉
    2020-11-28 20:19

    As many others have pointed out here, increasing the timeout settings for NGINX can solve your issue.

    However, increasing your timeout settings might not be as straightforward as many of these answers suggest. I myself faced this issue and tried to change my timeout settings in the /etc/nginx/nginx.conf file, as almost everyone in these threads suggest. This did not help me a single bit; there was no apparent change in NGINX' timeout settings. Now, many hours later, I finally managed to fix this problem.

    The solution lies in this forum thread, and what it says is that you should put your timeout settings in /etc/nginx/conf.d/timeout.conf (and if this file doesn't exist, you should create it). I used the same settings as suggested in the thread:

    proxy_connect_timeout 600;
    proxy_send_timeout 600;
    proxy_read_timeout 600;
    send_timeout 600;
    

提交回复
热议问题