Forum Discussion
What_Lies_Bene1
Nov 07, 2012Cirrostratus
OK, just FYI a Pool Member that is disabled will continue to service any existing connections until they are closed or time out, but will not receive new connections (except persisted connections I think).
Keep in mind that persistence effectively bypasses load balancing.
I believe even when a monitor marks a Pool Member as down, if you have Action on Service Down set to the default value of None, then existing and possibly persisted connections will continue to work as long as the F5 sees data being sent and received to and from that Pool Member. OneConnect overcomes this by making a persistence decision on each request (and thus load balancing each request) within a connection, not just when the connection is initially established and it won't persist to a node marked as down or disabled.
Does that make sense?