Forum Discussion
Nov 07, 2012
Hi Steve!
Thanks again for your answer!
It partly makes sense but there's a few things I still don't understand and I'd greatly appreciate your take on them.
"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)." - They were never enabled.
"Keep in mind that persistence effectively bypasses load balancing." - No persistence profile was assigned but perhaps that does not matter in this case?
"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." - The Action-On service down was set to "Reject".
"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." - This is very interesting, I will be reading some documentation about it.
Is it not a bit weird that LB_FAILED does not trigger for subsequent requests when the nodes are constantly down?
Again, thanks for your answers, they are much appreciated!
Kind regards,
Patrik