NGINX:上游超时(110:连接超时)，同时从上游读取响应头

问题描述：

我让Puma作为上游应用程序服务器运行，而Riak作为我的后台数据库集群.当我发送一个请求以减少约25K用户的数据块并将其从Riak返回到应用程序时，在Nginx日志中出现错误:

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 it from Riak to the app, I get an error in the Nginx log:

读取时上游超时(110:连接超时) 来自上游的响应头

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

如果我在没有nginx代理的情况下直接查询上游，并且请求相同，则会获得所需的数据.

If I query my upstream directly without nginx proxy, with the same request, I get the required data.

一旦放置代理，就会发生Nginx超时.

The Nginx timeout occurs once the proxy is put in.

**nginx.conf**

http {
    keepalive_timeout 10m;
    proxy_connect_timeout  600s;
    proxy_send_timeout  600s;
    proxy_read_timeout  600s;
    fastcgi_send_timeout 600s;
    fastcgi_read_timeout 600s;
    include /etc/nginx/sites-enabled/*.conf;
}

**virtual host conf**

upstream ss_api {
  server 127.0.0.1:3000 max_fails=0  fail_timeout=600;
}

server {
  listen 81;
  server_name xxxxx.com; # change to match your URL

  location / {
    # match the name of upstream directive which is defined above
    proxy_pass http://ss_api; 
    proxy_set_header  Host $http_host;
    proxy_set_header  X-Real-IP  $remote_addr;
    proxy_set_header  X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_cache cloud;
    proxy_cache_valid  200 302  60m;
    proxy_cache_valid  404      1m;
    proxy_cache_bypass $http_authorization;
    proxy_cache_bypass http://ss_api/account/;
    add_header X-Cache-Status $upstream_cache_status;
  }
}

Nginx有很多超时指令.我不知道我是否缺少重要的东西.任何帮助将不胜感激....

Nginx has a bunch of timeout directives. I don't know if I'm missing something important. Any help would be highly appreciated....

答

之所以会发生这种情况，是因为您的上游需要太多时间来回答请求，而NGINX认为上游已经无法处理该请求，因此它会返回错误. 只需在location配置块中包含并增加proxy_read_timeout. 同样的事情发生在我身上，我在工作中使用一个内部应用程序超时1小时:

This happens because your upstream takes too much to answer the request and NGINX thinks the upstream already failed in processing the request, so it responds with an error. Just include and increase proxy_read_timeout in location config block. Same thing happened to me and I used 1 hour timeout for an internal app at work:

proxy_read_timeout 3600;

这样，NGINX将等待一个小时(3600秒)以使其上游返回内容.

With this, NGINX will wait for an hour (3600s) for its upstream to return something.

NGINX:上游超时(110:连接超时)，同时从上游读取响应头

相关推荐