nanamikon opened a new issue, #7301:
URL: https://github.com/apache/apisix/issues/7301
### Description
Hi all
We know that websocket will pass data through tcp after upgrade through
http， so load balance by “**active tcp connection** should be most effective。
Refer to nginx doc about least_conn
`Specifies that a group should use a load balancing method where a
request is passed to the server with the least number of active connections,
taking into account weights of servers. If there are several such servers, they
are tried in turn using a weighted round-robin balancing method.`
Active connection mean there is http request on the way, and I find
it the same in the apisix and kong implement。 However， it is ineffective
against websocket， beacause there is no http request after upgrade.
Especially in the expansion situation, the new node can not get more connection
than other nodes.
Any tips to implement a new loadbalance to recover this situation？
Many Thanks
### Environment
- APISIX version (run `apisix version`): 2.9
- Operating system (run `uname -a`):
- OpenResty / Nginx version (run `openresty -V` or `nginx -V`):
- etcd version, if relevant (run `curl
http://127.0.0.1:9090/v1/server_info`):
- APISIX Dashboard version, if relevant:
- Plugin runner version, for issues related to plugin runners:
- LuaRocks version, for installation issues (run `luarocks --version`):
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
