Pools and Persistence

No, the pool command only "sets" the pool to use.

 

 

Answering your question is a little more tricky though. This is because it depends on what other profiles are in play. Basically, a connection is accepted up through the layers and when that finally reaches the proxy, the LB decision is made.

 

 

So, for example, you might select the pool in CLIENT_ACCEPTED. This doesn't mean that the load-balancing will occur at the end of the CLIENT_ACCEPTED event, because if you have HTTP also configured then the HTTP_REQUEST event is triggered first. So, you could actually change the pool selection again in the HTTP_REQUEST event. Generally, there's not another layer above HTTP, so, usually the load-balance does happen after HTTP_REQUEST. But, you can't always count on that. For example, there is the XML profile that might hold until a certain XML tag is found and can then influence the load-balance decision.

 

 

Thanks for asking this. It just goes to show that there is probably at least some misundertanding about it. Also, I'm sure you were probably thinking this was the case because 4.x worked like that.

 

 

HTH