Forum Discussion
Chris_Miller
Altostratus
Aug 16, 2010Why does "Forced Offline" finish off active connections
I've come to realize that most people in my environment believe forcing a node offline ends all connections. In our case, if we have a server with bad data, we don't want anyone with an established co...
George_Watkins_
Aug 16, 2010Historic F5 Account
Hi Chris,
The disabled option is to drain connections from the selected pool member. This is used in a lot of shops where user sessions are origin server specific. Most of the time, an operator would disable the relevant pool members, wait some length of time, then force the rest of the connections offline.
If you want to truly kill off every active connection to a pool member, you need to go to the origin server and manually stop the service in question.
I'd say that if you aren't using persistence and your connections are short-lived this shouldn't be much of a problem. If it is a longer-lived connection (streaming media or binary data), then it is a bit more difficult to handle gracefully.
-George
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects