Reindex Jira Data Center without downtime

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform Notice: Data Center Only - This article only applies to Atlassian products on the data center platform.

Purpose

This article instructs how to perform a full re-index on JIRA Data Center such that users are not impacted by the downtime of one node (whilst the indexing operation is completed).

Solution

  1. Ensure the node has a 'back-door' connector in it. This is an alternate HTTP connector that is not connected to the load-balancer / proxy, as detailed in Integrating JIRA with Apache in the Configure Tomcat section.
  2. Remove the node from the load-balancer configuration, so clients are still not being redirected to it.
  3. Access the node using the 'back-door' connector, and perform a 'lock JIRA and re-build index' as per Search Indexing.
  4. When the index has complete, access the node and verify everything is OK.
  5. If so, add the node back to the load-balancer configuration.

Solution2 

Applicable if: you are using JIRA 7.1+ and your LB is configured to use /status health-check call.

  1. Connect to any node and run  'lock JIRA and re-build index' as per Search Indexing.
  2. Node health-check status will be changes to '{"state":"MAINTENANCE"}' and node will be removed from LB. 
    1. There currently a bug in JIRA 7.6+ where the Status Code 500/503 will be returned instead, see  JRASERVER-67138 - Getting issue details... STATUS

After end of full reindex process, The index will be propagated to the other nodes provided everything is OK with the shared home configuration and the instances are able to communicate with each other.

Whilst the foreground index node is in progress, if other nodes make indexing changes they will kept track of in the database. Once the foreground indexing node has finished, the additional index changes will be replayed and integrity of the indexes is maintained across the cluster.

Due to  JRA-59721 - Getting issue details... STATUS  please update to JIRA 6.4.13 or later before performing a no downtime re-index.

DescriptionThis article instructs how to perform a full re-index on JIRA Data Center such that users are not impacted by the downtime of one node (whilst the indexing operation is completed).

Last modified on Sep 25, 2019

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.