Member ratio & dynamic LB alogithms

Hello Peter,

 

 

I'm not sure if I'm missing something here but I don't think you can use Ratio (member) and Least Connections together, they're set across the pool as a load balancing method and are therefore mutually exclusive. Do correct me if I've missed something!

 

 

Ratio is normally used when you know that member B is three times as fast, on average, as member A at serving requests (for example).

 

 

When you make use of Priority Group Activation, and if you set 'Less than 2' (as per your above example) and all pool members are available member A won't get used. However, if and when one of the other servers fails, there are no less than 2 members available in the (priority 3) group, and so member A comes online. You can have as many priority groups as you wish and create a cascading effect. The idea is that if the pool members are unreliable or often taken offline for maintenence, there will be other servers that can take their place whilst they are absent from the pool.

 

 

Let us know if you need anything else!