I have a configuration where I see the number of sessions are evenly distributed to backend server however number of Bytes In and out are very different for all backends. Which is causing uneven load on the backend server and one ends up getting 4k requests however other one gets 10k.
I am using 1.5.8 version with Keepalive and http_tunnel option. Please suggest me how to go about this issue.
Haproxy can send new requests to the server with the lowest number of concurrent sessions (balance leastconn), and if you don’t want keep-alive to the server to also have the same amount of transactions per server, then don’t use tunnel mode or keep-alive mode, use http-server-close mode instead.
But how many bytes come in and out of the server doesn’t affect the load-balancing process in haproxy, and it also doesn’t make a lot of sense.
We are facing some issue while running HAPROXY our environment.
1.Currently we are using the HAPROXY 1.8 build following are the problems we need to solve basically.
a.> Connection closing should happen with FIN rather than RSTs
b.> Even load balancing based on both session and request in and request out.
Please help us in achieving both these.
Currently we are using two configs in our HAPROXY.
in the frontend block we are using the “option http-tunnel” and in the backend we are using the “option http keep-alive” and also “no http-tunnel”
With the current above setup we can achieve point a , but in point b we can achieve session based even load balancing not request in and request out.