Forum Discussion
Vishnu_Palanis1
Nimbostratus
Mar 11, 2009Member reselect based on member status
Version of Big-IP is BIG-IP 9.1.2 Build 40.6
Here's the pseudo code for what I'm trying to do -
event http_request {
if pool member status is down {
[...
Vishnu_Palanis1
Nimbostratus
Mar 14, 2009Thanks for your replies.
"New requests should not be sent to a pool member that's marked down." - Actually, it's new *connections* that will not be
established to a pool member that's marked down.
Same with the "Action on Service Down" setting. This setting seemed to affect new connections only, when I tested this. I will test this out again.
A little more on my situation -
The client establishes a connection and keeps it open, and sends many requests over time on the connection. The Server(HTTP) has an idle timeout on all connections, and closes it after 2 minutes of inactivity. The client sends a few requests per minute, which results in the connection being kept open forever.
This is a difficult situation - the server cannot be shutdown for maintenance with open connections, since there maybe in flight requests over a connection. The server is able to force a health check failure and the pool member can be marked down. However, this only prevents new connections to be established on the server but does not prevent new requests over an existing connection.
I would like to prevent new requests to be sent to the server, so the server can expire the connection when the idle timeout kicks in.
Ideas?
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)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
