Symptoms

When you add cloud nodes provided by Application Connector to a pool using any load balancing algorithm other than Round Robin, load balancing fails and all traffic is directed to the first pool member in the list. This may also either prevent traffic from going to the cloud nodes , or force 100% of the traffic to the cloud nodes, if the cloud pool members co-exist with local pool members in the pool.

Impact

Since cloud pool members from Application Connector have no pool member statistics, all of the statistical load balancing methods will fail because the stats will read 0. For example if the load balancing method is Least Connections, the first pool member will always have 0 connections associated with it so all traffic will go to the first pool member.

Conditions

Cloud nodes provided by Application Connector exist in a pool, and the pool's load balancing method is not Round Robin.

Workaround

Always use Round Robin load balancing with cloud nodes provided by Application Connector.

Fix Information

None

Behavior Change