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

      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"

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

                Created:
                Updated:
                Resolved: