For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

jiseruk_43901's avatar
jiseruk_43901
Icon for Nimbostratus rankNimbostratus
Nov 14, 2013

Disable pool member when using HTTP/1.1

Hi. We are using HTTP/1.1 from the client to the backends servers. When I disable a member from a pool, it`s still receive requests thru the active connections and there`s no way I can´t stop it unt...
devops
iControl
management
Andy_Litzinger's avatar
Andy_Litzinger
Nov 14, 2013

I think you can achieve what you want by turning on a OneConnect profile. Then each request gets load balanced instead of each TCP session. so when you disable a pool member the LTM will stop sending requests to that member even though it may still have active TCP sessions that haven't timed out yet. There are other trade-offs to using OneConnect so be sure to read up on on it, but I think it will solve the problem you describe. You can also achieve per request load balancing using LB::detach in an iRule.