Nginx和多个流星/ Nodejs应用程序的麻烦

2 回答

• 27

  proxy_pass http://127.0.0.1:8002/1;  <-- these should be 
  proxy_pass http://**my_upstream_name**;  <--these
  

  then

  upstream my_upstream_name {  
  
  //Ngixn do a round robin load balance, some users will conect to / and othes to /app2
  
  server 127.0.0.1:8001;
  
  server 127.0.0.1:8002;
  
  }
  

  一些 tips 控制代理：

  看看here @nginx docs

  然后我们走了：

  weight = NUMBER - 设置服务器的权重，如果没有设置权重等于1 . 不 balancer 默认循环 .

  max_fails = NUMBER - 在一段时间内（由参数fail_timeout分配）尝试与服务器通信失败的次数，之后认为它不起作用 . 如果未设置，则尝试次数为1 . 值为0将关闭此检查 . 被认为是失败的是由proxy_next_upstream或fastcgi_next_upstream定义的（除了不计入max_fails的http_404错误之外） .

  fail_timeout = TIME - 必须发生的时间* max_fails *与服务器通信失败的次数导致服务器被视为无效的次数，以及服务器被视为无效的时间（在进行另一次尝试之前） . 如果未设置，则时间为10秒 . fail_timeout与上游响应时间无关，使用proxy_connect_timeout和proxy_read_timeout来控制它 .

  down - 将服务器标记为永久脱机，以与指令ip_hash一起使用 .

  backup - （0.6.7或更高版本）仅在非备份服务器全部关闭或忙碌时才使用此服务器（不能与指令ip_hash一起使用）

  EXAMPLE generic
  
      upstream  my_upstream_name  {
        server   backend1.example.com    weight=5;
        server   127.0.0.1:8080          max_fails=3  fail_timeout=30s;
        server   unix:/tmp/backend3;
      }
  //   proxy_pass http://my_upstream_name;
  

  tho these is what you need:

  如果你只想控制一个应用程序的vhost之间的负载：

  upstream  my_upstream_name{
            server   127.0.0.1:8080          max_fails=3  fail_timeout=30s;
            server   127.0.0.1:8081          max_fails=3  fail_timeout=30s;
            server   127.0.0.1:8082          max_fails=3  fail_timeout=30s;
            server   127.0.0.1:8083 backup;
  //  proxy_pass http://my_upstream_name; 
  // amazingness no.1, the keyword "backup" means that this server should only be used when the rest are non-responsive
      }
  

  if u have 2 or more apps: 1 upstream per app like:

  upstream  my_upstream_name{
                server   127.0.0.1:8080          max_fails=3  fail_timeout=30s;
                server   127.0.0.1:8081          max_fails=3  fail_timeout=30s;
                server   127.0.0.1:8082          max_fails=3  fail_timeout=30s;
                server   127.0.0.1:8083 backup;  
              } 
  upstream  my_upstream_name_app2  {
                server   127.0.0.1:8084          max_fails=3  fail_timeout=30s;
                server   127.0.0.1:8085          max_fails=3  fail_timeout=30s;
                server   127.0.0.1:8086          max_fails=3  fail_timeout=30s;
                server   127.0.0.1:8087 backup; 
              } 
  upstream  my_upstream_name_app3  {
                server   127.0.0.1:8088          max_fails=3  fail_timeout=30s;
                server   127.0.0.1:8089          max_fails=3  fail_timeout=30s;
                server   127.0.0.1:8090          max_fails=3  fail_timeout=30s;
                server   127.0.0.1:8091 backup;  
              }
  

  希望能帮助到你 .

  回复于 2024-05-06T03:40:02+08:00
• 0

  人们正在为Nginx寻找替代方案：为每个Meteor应用程序安装群集包，该包将自动处理负载 balancer . https://github.com/meteorhacks/cluster

  如何设置：

  # You can use your existing MONGO_URL for this
  export CLUSTER_DISCOVERY_URL=mongodb://host:port/db,
  # this is the direct URL to your server (it could be a private URL)
  export CLUSTER_ENDPOINT_URL=http://ipaddress
  # mark your server as a web service (you can set any name for this)
  export CLUSTER_SERVICE=web
  

  示例设置：

  {
    "ip-1": {
      "endpointUrl": "http://ip-1",
      "balancerUrl": "https://one.bulletproofmeteor.com"
    },
    "ip-2": {
      "endpointUrl": "http://ip-2",
      "balancerUrl": "https://two.bulletproofmeteor.com"
    },
    "ip-3": {
      "endpointUrl": "http://ip-3",
      "balancerUrl": "https://three.bulletproofmeteor.com"
    },
    "ip-4": {
      "endpointUrl": "http://ip-4"
    }
  }
  

  回复于 2024-05-06T03:40:02+08:00