[GitHub] [apisix] thor533 commented on issue #7088: bug: Least-connection result is incorrect

["thor533 (via GitHub)" <gi...@apache.org>]

thor533 commented on issue #7088:
URL: https://github.com/apache/apisix/issues/7088#issuecomment-1518924274

   > hi，[zssangglass](https://github.com/tzssangglass)；thanks for your quick reply。 my test result is different with you in the concurrent case ; follow is my test case:
   > 
   > this is my test network topo for least-conn，the client is jmeter，
   > 
   > client ------apisix---------servive node（189 and 124 node，two nodes in LAN）
   > 
   > case1: node 189 : weight 1 ; node 124 : weight 2 sent 20 requests from client to apisix；all the request is concurrent with different session(we capature the packets, so, can confirm this) ; Simultaneously， capature packets with tcpdump in apisix,node 189,124。 finally，we find all the requests arrive at node 124， no packet to node 189。 we repeat the test case muti-times，the result is same. my test case is near to the real case，so why the result is different with yours?
   
   When I use postman to click consecutively, this active_conn should always be 0. According to (active_conn +1) /weigth, we know that they should have the same score。
   With the same minimum number of connections, is a normal polling algorithm used or SWRR？


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org