F5 hardware load balancers currently run round robin on our production nodes. If a node is down or in recovery, attempted connections cause an exception with some of our applications where retry/failover/connection pools are not implemented.
Looking for best practices/tests as to health check for avoiding attempted connections to nodes not in 'UP' state.
Best practices/tests as to health check for avoiding attempted connections F5 Load Balancer
Sign up
Already have an account? Login
Welcome to the Rocket Forum!
Please log in or register:
Employee Login | Registration Member Login | RegistrationEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.