Forum Discussion
NimbostratusSpeeding connection draining by forcibly closing http keep-alive?
It is a common pattern when doing rolling restarts/changes to members of a HTTP pool to take a member out of service, wait for connections to drop to zero, then do your maintenance there and put it back in the pool. However, because of http keep-alive I assume, it often takes minutes for HTTP client connections to drain even if they are not very active. I'd prefer not to disable http keep-alive entirely. Is it possible to set a profile, monitor, or iRule that would force keep-alive: close to be sent to clients connected to pool members that meet the criteria (monitor test failing, static page returns certain string, etc)?
3 Replies
Vijay_ECirrus
More than HTTP Keepalive, it is the persistence that could cause connection to last longer on a pool member. You can use "forced-offline" or "reselect" option within the pool to select another pool member, if your application can handle the transition.
fenderb_312187The oneconnect profile w/Reselect action on service down was a good solution. Thank you!
- Vijay_E
Welcome ! :)
