Uploaded image for project: 'Nuxeo Studio'
  1. Nuxeo Studio
  2. NXS-5548

Create more resilient Status Servlet

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Critical
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: 3.20.1
    • Component/s: Infrastructure
    • Tags:
    • Story Points:
      2

      Description

      The current Status Servlet has two possible OK response:

      • Servlet loaded: basically Tomcat stated.
      • Runtime started: basically components loaded but not started.

      Issue is Runtime started doesn't mean all the components are correctly started. For instance, database and ACL vacuuming not done.

      In the context of a cluster, especially with NOS, we identified in NXCONNECT-2182 that it could lead to having node blocked at startup. (Trying to read ACL because of a query when vacuuming is in progress)

      We are overriding the current StatusServlet for having a OK state at the end of all components.

        Attachments

          Activity

            People

            • Assignee:
              akervern Arnaud Kervern
              Reporter:
              akervern Arnaud Kervern
              Participants:
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                PagerDuty

                Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.