> On 8 мая 2015 г., at 4:54, Frank Schubert <f.schub...@gmail.com> wrote: > > Hi, > > first of all let me thank you for an amazing piece of software. I like > working with haproxy a lot! > > My problem: The weight setting for a backend seems to be ignored when the max > concurrent session setting is reached. I was expecting the connection to get > queued for this backend but it seems to flip over to the host that has > connections available. > > I simplified my setup to 2 backend smtp servers, one with weight 100, the > other with weight 1. The max connection setting is set to 2. I'm opening > multiple SMTP connections simultaneously to this haproxy server. Attached > screenshot from haproxy stats shows that backend with weight 1 gets way too > many sessions. > > Increasing max concurrent sessions to 5 or more seem to prevent this > behavior, but I'm not totally sure about this. > > I would like to have only a small fraction (100:1) of requests go to the > backend with the lower weight and wonder how to do this correctly. It's more > important to me to have a defined distribution of connections going to > backends than answering requests as quickly as possible regardless of what > backend is used. > > <haproxy-distribution-ignores-weight.jpg> >
This screenshot also illustrates incorrect Max Request Rate calculation I reported 2 years ago: http://www.serverphorums.com/read.php?10,623596
