Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-67138

/status url returns ERROR instead of MAINTENANCE during foreground reindexing

    XMLWordPrintable

Details

    Description

      Summary

      <JIRA>/status returns ERROR during full re-indexing (foreground reindexing).
      This makes a host that is doing a full re-index is indistinguishable from a host that is not healthy (i.e. not live) and needs restarting.

      Steps to Reproduce

      1. Start 'Lock JIRA and rebuild index' (make sure you have enough issues to reindex)
      2. Trigger call to <JIRA>/status

      Expected Results

      HTTP code: 200
      Body:

      {"state":"MAINTENANCE"}

      Actual Results

      HTTP code: 500 or 503
      Body:

      {"state":"ERROR"}

      Notes

      • Same "ERROR" status was not reproducible in earlier Jira version like Jira v7.2.12
      • Background reindex returns "RUNNING" status

      Workaround

      None

      Note on fix

      The behaviour of this endpoint in versions of Jira containing this fix is (from comment below):

      • No Johnson event, or a Johnson event which doesn't prevent startup: 200, "STARTING"/"FIRST_RUN"/"RUNNING"
      • Startup is delayed by a reIndexing event, and nothing else: 503, "MAINTENANCE"
      • Startup is prevented by a different Johnson event: 500, "ERROR"

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-47045 When a re-indexing node is abruptly stopped indexing still shows as in progress on other nodes, preventing future reindexing

          • High - High priority issues
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-59503 /status should return running and not starting when JDC node is already started up

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-62927 If JIRA has errors during startup, ApplicationStatusServlet doesn't show JIRA state properly and remains stuck in {"state":"STARTING"}

          • Low - Low priority issues
          • Gathering Impact

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-65708 /status returns Maintenance instead of Running when nodes are not in Maintenance mode and the Database is configured with an unsupported collation

          • High - High priority issues
          • Long Term Backlog
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-67135 JIRA Data Center node appear as Active when shutdown ungracefully

          • Low - Low priority issues
          • Closed

          Suggestion - JRASERVER-66970 /status should indicate when indexes are broken on a node

          • Closed

          Suggestion - JRASERVER-63928 Document the /status URL for JIRA

          • Gathering Interest

          Suggestion - JRASERVER-64269 As an JIRA Administrator I want JIRA datacenter health-check to change status code

          • Gathering Interest
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Activity

            People

              tom@atlassian.com Tom Davies
              sluo@atlassian.com Sasa Luo (Inactive)
              Votes:
              19 Vote for this issue
              Watchers:
              41 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: