Health check: Fresh index snapshot existence
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
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
Purpose
The fresh index snapshot existence health check verifies that the most recently modified index snapshot present in the shared home directory isn’t older than the configured maximum age. This helps ensure that in a failover scenario, the node that takes over from the failed node can quickly acquire the most recent possible index without the need for a full re-indexing operation.
Learn more about the index startup procedure in Jira 9.4 and later
Health check results
| Icon | Result | What this means |
|---|---|---|
 | All checks have passed successfully. | The shared home directory contains an index snapshot newer than the configured maximum age. |
 | The shared home directory doesn’t contain a fresh index snapshot. Autoscaling may fall back to the legacy mode of adding a new node to the cluster. | The latest index snapshot stored in the shared home directory is older than the configured maximum age (8 days by default). |
| Couldn't access index snapshot files. Autoscaling may fall back to the legacy mode of adding a new node to the cluster. | Jira can’t read the list of files in the snapshot directory. |
Resolution
Here’s what you can do depending on the reason why the health check has failed in your system:
The shared home directory doesn’t contain a fresh index snapshot
Create the index snapshot manually. Learn how to create an index snapshot manually
You can change the maximum age of an index snapshot by setting the system property -Dcom.atlassian.jira.startup.max.age.of.usable.index.snapshot.in.hours.
Couldn’t access index snapshot files
Ensure that Jira has the correct read permissions to access the snapshot directory.
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.
In the event that the directory is reported as missing but does exist on the file system:
[directory] showing ownership. This can be achieved through the following steps:Linux
ls -lahR [directory] | gzip -9 > fileListing.gzWindows
Use the AccessEnum SysInternals tool by Microsoft to complete this task, and collect a screenshot showing the permissions of the Shared Directory being used.