F5 connection limit and queuing, unexpected behavior
I setup the F5 to limit the number of connections to each member server in the pool associated with the VIP and configured them each with a connection limit of 500. Then I turned on in the pool Enable Request Queuing. However, I ran into a issue where each member server in the pool showed that the server had hit their connection limit and were taken out of service. But, when the server team looked at the servers they didn't see any connections except a handful, but it did appear that the F5 was queuing the traffic. Is there something else that needs to be modified to prevent that issue? The servers normally on average have only about 300 connection each. I am trying to figure out why the F5 didn't see that the servers had no connections and forward the connections?