Forum Discussion

Stephen_Kaiser's avatar
Stephen_Kaiser
Icon for Nimbostratus rankNimbostratus
Apr 19, 2021

vIP Queue not releasing connections

I've configured a vIP with a default pool, created an iRule that inspects the http:payload, and routed certain requests to a second pool based on the payload contents. This was working perfectly unti...
application delivery
BIG-IP
iRules
Stephen_Kaiser's avatar
Stephen_Kaiser
Icon for Nimbostratus rankNimbostratus
Apr 19, 2021

I did not. I'll use those in my future testing, thank you. I'm attempting to reproduce the issue on our test environment but so far I've had no luck breaking it again in the same way.

 

However, I would expect issues of that nature to cause problems with any pools targeting those servers, and also cause the health monitors to fail. But the issue only presented in the website_search pool, not the default_pool, and not in the health monitors. The default pool and the website_search pool dedicated to website searches point at the same server nodes. The only difference between the two pools is the connection limit on each member server and the queue timeouts.

  • default_pool:
    • Queue timeout: 30000ms
    • Queue depth: 3000
    • member_server_1:
      • Connection limit: 80
    • member_server_2:
      • Connection limit: 80
    •  
  • website_search:
    • Queue timeout: 15000ms
    • Queue depth: 3000
    • member_server_1:
      • Connection limit: 20
    • member_server_2:
      • Connection limit: 20
  • Nikoolayy1's avatar
    Nikoolayy1
    Icon for MVP rankMVP
    Apr 20, 2021

    For issues like the F5 connectioon table not timing out or the Time_Wait only the data plane will be affected not the control plane ( health monitoring ) as they are a sepate thing.

     

     

    If the issue was with the connection limit, then you should be having non stop issues, also to protect the servers from connection exaustion attack the "Slow Ramp Time" is a better option.

     

     

    https://support.f5.com/csp/article/K14804

     

     

     

     

    You may also check irule if it is freeing the HTTP data with log local0 (it should do so during the "HTTP_REQUEST_DATA" event but just in case). Maybe adding HTTP::release at the end just to make certain that the collected data is released.

     

     

    https://clouddocs.f5.com/api/irules/HTTP__release.html

     

    https://support.f5.com/csp/article/K55131641

     

    https://clouddocs.f5.com/api/irules/HTTP_REQUEST_DATA.html

     

     

     

     

    Also you may check the bug tracker if there bugs matching you simptoms and version for "HTTP_REQUEST_DATA", "HTTP::payload" , "HTTP::collect" , etc.

     

     

    https://support.f5.com/csp/bug-tracker