用于平衡Node Js的HaProxy配置 - WebSockets

时间:2014-08-08 14:21:58

标签: node.js haproxy

我刚刚在我的Debian系统上安装了HaProxy 1.6,我想用它来分发WebSocket(WS://)连接。系统正在运行同一WebSocket服务的5个服务器实例;这些实例具有相同的IP地址但具有不同的端口:

192.168.10.1:801
192.168.10.1:802
192.168.10.1:803
192.168.10.1:804
192.168.10.1:805

我正在寻找一些建议来创建一个简单的配置文件来侦听端口800上的请求并在服务器之间平均分配(可能是?)。

defaults
    mode http
    # Set timeouts to your needs
    timeout client  5s
    timeout connect 5s
    timeout server  5s

frontend all 0.0.0.0:800
    mode http
    timeout client 120s

    option forwardfor
    # Fake connection:close, required in this setup.
    option http-server-close
    option http-pretend-keepalive

    acl is_sockjs path_beg /echo /broadcast /close
    acl is_stats  path_beg /stats

    use_backend sockjs if is_sockjs
    use_backend stats if is_stats
    default_backend static


backend sockjs
    # Load-balance according to hash created from first two
    # directories in url path. For example requests going to /1/
    # should be handled by single server (assuming resource prefix is
    # one-level deep, like "/echo").
    balance uri depth 2
    timeout server  120s
    server srv_sockjs1 127.0.0.1:12345
    # server srv_sockjs2 127.0.0.1:9998

backend static
    balance roundrobin
    server srv_static 127.0.0.1:801

backend stats
    stats uri /stats
    stats enable

我设法通过使用上面已经下载的配置文件以某种方式使其工作..但它看起来太复杂了我,并且一次只接受一个连接。如果第二个客户端连接,则HA代理断开前一个/第一个,并连接一个新的/第二个..

1 个答案:

答案 0 :(得分:1)

最简单的方法是为所有的websocket机器定义一个后端,并围绕它们进行循环,如下所示:

frontend ft_web
  bind 192.168.10.1:800 name http
  maxconn 10000
  default_backend bk_web

backend bk_web                      
  balance roundrobin
  server websrv1 192.168.10.1:801 maxconn 10000 weight 10 cookie websrv1 check
  server websrv2 192.168.10.1:802 maxconn 10000 weight 10 cookie websrv2 check
...

如果它没有用,似乎你的超时时间太短,试着像这样定义它们:(默认情况下)

 timeout client          25s
  timeout connect          5s
  timeout server          25s
# timeout tunnel available in ALOHA 5.5 or HAProxy 1.5-dev10 and higher
  timeout tunnel        3600s
  timeout http-keep-alive  1s
  timeout http-request    15s
  timeout queue           30s
  timeout tarpit          60s