Hi,

Nope. I was trying to see what I can do about this, so I removed the leastconn (reverting back to round-robin) then configured leastconn back, but without slow-start parameter. What I immediately noticed is that servers started to be hit in a more equal manner, which is what I expected. I then reapplied the leastconn command, but with slow-start parameter and it would seem that session distribution was as expected. I assume that maybe removing and reapplying leastconn command did the trick, or maybe slow-start parameter was somehow misbehaving when I first applied it....

Now what I noticed is there are some sessions under failure column of "show serverfarm" output and I don't believe I had those before I switched to leastconn. The number is very low, like 5 failed versus 30,000 total, but still I was wondering if there is anything different with leastconn from round-robin that would cause some of the sessions to fail ?

Thanks!

David

David,

we have a few slowstart issue where the internal data structure could get corrupted preventing some servers to receive traffic.

You may have hit such a problem.

CSCsx80991: ACE: Leastcon negative weight after adding new rservers

Usually, removing/adding the predictor does fix the problem.

Next time you see the issue, you should open a service request to receive guidance on what information to collect.

The procedure is not as easy as show ....

Regarding the failure, it is independent of the predictor.

We count a failure when the connection can't be established.

Reset from server or no response.

Gilles.