Advice on "persist hash" load balancing

I just wanted to clarify, that each HTTP request is parsed and inspected, regardless of whether or not the OneConnect profile is attached. However, without OneConnect, a new LB decision is not made unless the pool changes. So, even though you mave now have new criteria that should dictate a new pool member be used, it does not detach to previous one. However, one of the aspects of OneConnect is that each request is load-balanced to a potentially new member (depending on the lb mode) and persistence is taken into account during the load-balancing decision.

 

 

HTH.