Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-67161

Router pods restart upon hitting maxconn

    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • Critical
    • None
    • x86_64
    • Production
    • None
    • None
    • Rejected
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      The Ingress Router pods are experiencing instability under high load. Specifically, whenever the configured maximum connection limit (maxconn) is saturated, the liveness probe fails and pods terminate and restart instead of gracefully throttling traffic.

      Version-Release number of selected component (if applicable):

      latest

      How reproducible:

      With an existing route, generate a load over maxconn, we used https://github.com/mparram/test-backend?tab=readme-ov-file#run-in-openshift    

      Steps to Reproduce:

          1. Install and configure https://github.com/mparram/test-backend?tab=readme-ov-file#run-in-openshift
          2. Set the maxconn to 2000 (optional)
          3. Scale the replicas enough to reach maxconn on haproxy (could be checked looking at haproxy_frontend_current_sessions metric)
          4. Review the haproxy behavior
          

      Actual results:

      The Kubelet restarts the HAProxy container following a liveness probe failure.

      Expected results:

      Haproxy gracefully throttling traffic.    

      Additional info:

          

              alebedev@redhat.com Andrey Lebedev
              rhn-support-jortizpa Jose Ortiz Padilla
              None
              None
              Shudi Li Shudi Li
              None
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: