Elasticsearch:连接到上游时连接被拒绝

Question

我已经使用Kibana设置了一个Elasticsearch服务器来收集一些日志.

Elasticsearch是Nginx的反向代理,这里是conf:

server {   
  listen   8080;   
  server_name myserver.com; 
  error_log   /var/log/nginx/elasticsearch.proxy.error.log;
  access_log  off;

  location / {

    # Deny Nodes Shutdown API
    if ($request_filename ~ "_shutdown") {
      return 403;
      break;
    }

    # Pass requests to ElasticSearch
    proxy_pass http://localhost:9200;
    proxy_redirect off;
    proxy_http_version 1.1;
    proxy_set_header Connection "";

    proxy_set_header  X-Real-IP  $remote_addr;
    proxy_set_header  X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header  Host $http_host;

    # For CORS Ajax
    proxy_pass_header Access-Control-Allow-Origin;
    proxy_pass_header Access-Control-Allow-Methods;
    proxy_hide_header Access-Control-Allow-Headers;
    add_header Access-Control-Allow-Headers 'X-Requested-With, Content-Type';
    add_header Access-Control-Allow-Credentials true;

  }

}

一切运作良好,我可以curl -XGET "myserver.com:8080"检查,我的日志进来.

但每分钟左右,在nginx错误日志中,我得到了:

2014/05/28 12:55:45 [error] 27007#0: *396 connect() failed (111: Connection refused) while connecting to upstream, client: [REDACTED_IP], server: myserver.com, request: "POST /_bulk?replication=sync HTTP/1.1", upstream: "http://[::1]:9200/_bulk?replication=sync", host: "myserver.com"

我无法弄清楚它是什么,在conf中是否有任何问题会阻止某些_bulk请求通过？

Answer 1

似乎upstream和keepaliveES后端正常工作需要不同,我最终使用以下配置工作:

upstream elasticsearch {
    server 127.0.0.1:9200;
    keepalive 64;
}

server {

  listen 8080;
  server_name myserver.com;
  error_log   /var/log/nginx/elasticsearch.proxy.error.log;
  access_log  off;

  location / {

    # Deny Nodes Shutdown API
    if ($request_filename ~ "_shutdown") {
      return 403;
      break;
    }

    # Pass requests to ElasticSearch
    proxy_pass http://elasticsearch;
    proxy_redirect off;
    proxy_http_version 1.1;
    proxy_set_header Connection "";

    proxy_set_header  X-Real-IP  $remote_addr;
    proxy_set_header  X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header  Host $http_host;

    # For CORS Ajax
    proxy_pass_header Access-Control-Allow-Origin;
    proxy_pass_header Access-Control-Allow-Methods;
    proxy_hide_header Access-Control-Allow-Headers;
    add_header Access-Control-Allow-Headers 'X-Requested-With, Content-Type';
    add_header Access-Control-Allow-Credentials true;

  }

}