Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-46458

JIRA Data Center health check status URL doesn't accommodate for foreground indexing

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Problem Definition

      The URL that is suggested for use in JIRA Data Center behind a load balancer, as mentioned in https://confluence.atlassian.com/display/ENTERPRISE/JIRA+Data+Center+Load+Balancer+examples states to use /status and it will return "state":"RUNNING" for a healthy node that should be in the LB pool. In my testing, I found that when a node is performing a foreground re-index that locks JIRA, it is actually unavailable for processing user requests. Accessing a node that is performing a locking re-index redirects to an error page and gives an HTTP 503. When that is occurring, I would not want that node to have user requests routed to it.

      Suggested Solution

      Having multiple nodes for JIRA Data Center, we like foreground re-indexing as it is much faster with the amount of data we have. So when a node is locked for re-indexing we'd like it to take itself out of the pool. This issue is to suggest either:

      • the /status page be updated to provide a different status during indexing, possibly "state":"INDEXING". This would allow a LB health check to take the node out of the pool during indexing
      • update the Data Center LB documentation (above) to instruct users to use /secure/errors.jsp as the health check URL as it more accurately conveys whether a node is capable of servicing requests

          Form Name

            [JRACLOUD-46458] JIRA Data Center health check status URL doesn't accommodate for foreground indexing

            JIRA 7.1.9 returns MAINTENANCE during foreground re-index

            curl -v http://127.0.0.1:8081/status
            
            < HTTP/1.1 200 OK
            
            {"state":"MAINTENANCE"}
            

            Andriy Yakovlev [Atlassian] added a comment - JIRA 7.1.9 returns MAINTENANCE during foreground re-index curl -v http: //127.0.0.1:8081/status < HTTP/1.1 200 OK { "state" : "MAINTENANCE" }

            Looks like 7.1 is out (Feb 11), guessing this is baked into it? Thanks.

            David Hergert (PAYX) added a comment - Looks like 7.1 is out (Feb 11), guessing this is baked into it? Thanks.

            Otto added a comment -

            Hi David,
            The release management team is working through the release cut at the moment. Shouldn't be too much longer. Thanks for your patience.

            Otto added a comment - Hi David, The release management team is working through the release cut at the moment. Shouldn't be too much longer. Thanks for your patience.

            Is there an ETA on JIRA 7.1 release? Thanks!

            David Hergert (PAYX) added a comment - Is there an ETA on JIRA 7.1 release? Thanks!

            Cordo added a comment -

            Hi dhergert1,

            During a foreground reindex, during the period that users are prevented from accessing JIRA on that node, the /status page for that node will report the status as "state":"MAINTENANCE". Currently, only the foreground reindex reports this state, but it may be used in future to cover other planned maintenance tasks.

            Cordo added a comment - Hi dhergert1 , During a foreground reindex, during the period that users are prevented from accessing JIRA on that node, the /status page for that node will report the status as "state":"MAINTENANCE" . Currently, only the foreground reindex reports this state, but it may be used in future to cover other planned maintenance tasks.

            @otto - great, thanks! Out of curiosity, what was the chosen solution?

            David Hergert (PAYX) added a comment - @otto - great, thanks! Out of curiosity, what was the chosen solution?

            Otto added a comment -

            Thanks dhergert1 - Look out for this to be updated in a future release.

            Otto added a comment - Thanks dhergert1 - Look out for this to be updated in a future release.

            Thank you for the information. Step #2 of the workaround is "remove the node from the load-balancer configuration". That's what I'd like this status page to do, by doing a Lock and Re-Index and the 'health check' URL used by the load balancer pick up on that and take it out of the pool.

            David Hergert (PAYX) added a comment - Thank you for the information. Step #2 of the workaround is "remove the node from the load-balancer configuration". That's what I'd like this status page to do, by doing a Lock and Re-Index and the 'health check' URL used by the load balancer pick up on that and take it out of the pool.

            Taiwo Akindele (Inactive) added a comment - https://confluence.atlassian.com/display/JIRAKB/How+to+Re-Index+JIRA+Data+Center+without+Downtime may offer a workaround for this

              rcordova Cordo
              eee3c10257fb David Hergert (PAYX)
              Votes:
              3 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: