how can we modify the Source port as a client
Currently using azure load balancer to route print requests (using https) to one of four BarTender application servers (BAS). However, all print requests are going to the same BAS. Is there a way to change the source information so the load balancer will use other BAS?
How Load Balancer works?
Load balancer uses 5 tuple algorithm to distribute client requests by default. This algorithm is a 5 tuple (source IP, source port, destination IP, destination port, protocol type) hash to map traffic to available servers. It provides stickiness only within a transport session. Packets in the same TCP or UDP session will be directed to the same datacenter IP (DIP) instance behind the load balanced endpoint. When the client closes and re-opens the connection or starts a new session from the same source IP, the source port changes and causes the traffic to go to a different DIP endpoint.
If most of the load goes to a single instance, the number one reason is due to the testing client creating and reusing the same TCP connections. The Azure loadbalancer does round robin load balancing for new incoming TCP connections, not for new incoming HTTP requests. So when a client makes the first request to the cloudapp.net URL, the LB sees an incoming TCP connection and routes it to the next instance in the LB rotation, and then the TCP connection is established between the client and the server. Depending on the client app, all future HTTP traffic from that client will may go over the same TCP connection or a new TCP connection.
-
HELLO everyone i have an issue to convert the barcode 1D to Datamatrix in TOSHIBA BEX4T1 by BaS FILE and PRN FILE . anyone can help please PRINT #2, "{XB01;0400,0780,9,3,02,3,0050,+0000000000,000,0,00|}"
0 -
Please sign in to leave a comment.
Comments
2 comments