Thanks for reply.

You are correct. First HTTP request will not have any ACE Cookie , so i assume it will go to new available server. isnt it? The reason we used is, With this predictor only we are seeing Equal load balancing with 6 servers. Other Predictors Least Conns, Round Robin giving Unqual Load balancing and some of the users never been used.

So Please advise How Hash Cookie Predictor works here and how its giving good equal load balancing?

If an http request doesn't contain the expected cookie, ACE should do round robin. In that case, the server weight won't be taken into account.

You should try the following:

1/ configured round robin with cookie insertion

2/ clear the stats (clear serverfarm )

3/ genereat x requests

4/ check the serverfarm stats

5/ same steps with leastconn and hash predictor

Small q, does your traffic generator actually learn cookies?

Olivier

SO even if we have HASH COOKIE predictor in this case ACE will do round robin when it see no cookie in header right? Nothing will get dropp of from ACE i hope.

We tried with round robin and cookie insertion, Least connection  and hash predictor. Only Hash predictor gives good load balancing results.

I will ask Load ganarators about cookie clear option.  Do you see any difficulties of having HASH COOKIE predictor

Hi,

Even I used the same way ( pedictor as hash cookie and stickiness based on http cookie insertion)

for me too load balancing works perfectly fine.

now i am also amazed to see the reply....

So in this way , predictor is never invoked ?... in that case how is it equally load balancing ...

thanks,

Parvees

Your understanding is correct, in case a request doesn't contain the cookie name configured in the predictor, request won't be dropped. The round robin algorithm will be used instead.

The fact the hash cookie give better result that round robin is quite strange to me. I would recommend you to confirm this and open a TAC SR if this turns out to be indeed the case.

Parvees, with cookie insertion, the predictor is used to load balance requests that don't have the cookie. If a request contain the cookie, it is simply forwarded according to the sticky db.

--Olivier