Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-14341

The karaf health check uses the same servlet container as user traffic

XMLWordPrintable

    • % %
    • build3
    • Fuse On Openshift
    • Hide

      Deploy a container with some kind of REST or SOAP service that that a while to complete.

      Run a stream of requests, causing the queue to grow

      Wait for the probes to fail and the container to get restarted

      Show
      Deploy a container with some kind of REST or SOAP service that that a while to complete. Run a stream of requests, causing the queue to grow Wait for the probes to fail and the container to get restarted

      The Karaf health check / readiness check (https://github.com/jboss-fuse/fabric8/blob/3.0.11.redhat-7.x/components/fabric8-karaf/fabric8-karaf-checks/src/main/java/io/fabric8/karaf/checks/internal/ReadinessCheckServlet.java) uses the same servlet container as all of the rest of the http traffic coming into the container.

      If there is any kind of longer running request or a slow down or down stream processing delay, the worker queue can start to accumulate messages.

      When this happens, health and readiness checks become blocked at the end of queue which leads to probe failures and the container getting killed.

              ggrzybek Grzegorz Grzybek
              rhn-support-mrobson Matt Robson
              Luigi De Masi Luigi De Masi
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: