Cluster Index Replication health check fails in Jira Data Center
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Overview
In JIRA Data Center, the search index is replicated amongst other nodes automatically through the shared home. The Cluster Index Replication Health Check will check if the index that is used to provide results of searches for issues is up-to-date on all active nodes in the JIRA Data Center configuration. Each time a change is made in JIRA on a specific node, other nodes will need to be aware of these changes so that search results are up-to-date.
| Icon | Result | What this means |
|---|---|---|
 | The health check passed successfully. | The health check did not discover any problems with replication. |
 | Index replication for cluster node <node-name> is behind by <seconds> seconds. | The replication is out of date by greater than 2 minutes and less than 5 minutes. This may indicate a performance problem with the environment. |
 | Index replication for cluster node <node-name> is behind by <seconds> seconds. | The replication is out of date by greater than 5 minutes. The replication is either not occurring, or is critically slow. |
Troubleshooting
| Problem | Suggestion |
|---|---|
| The node(s) can not communicate with the database in a timely manner. | Check that all the nodes are correctly communicating with the database in a timely manner. This can be done by:
|
| There is unexpected data in the affected table. | Check the contents of the data in the database with the assistance of Atlassian Support. |
| The health check reports nodes to be behind by a number of seconds equal to the timezone offset. | The database server may be in a different timezone to the application servers. See this KB article for details. |
Providing Information to Support
In case you are unable to troubleshoot and fix the problem by yourself, please create a support ticket at support.atlassian.com and attach the following information to the ticket:
- Take a Screenshot of the Health Check results.
- Collect a Support ZIP from each of the Data Centre nodes.
- Any collected information from the suggestions in this document.
Additionally, collect the output from the following SQL and provide it with the data above:
SELECT max(id), node_id FROM replicatedindexoperation GROUP BY node_id;
SELECT * FROM nodeindexcounter;