Jira Service Crashes due to "Index Snapshot" failure

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

Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles 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

Summary

Jira Service crashes when Jira tries to create an "Index Snapshot".

Environment

Jira Data Center all versions.

Diagnosis

  • Reviewing the atlassian-jira.log, below "IOException" is observed while "Jira Index Snapshot" service tries to generate Snapshot.
2025-03-11 06:00:23,865+0000 Caesium-1-1 ERROR anonymous    JIRA Index Snapshot Service [c.a.jira.service.ServiceRunner] An error occurred while trying to run service 'JIRA Index Snapshot Service'. java.io.IOException: Entry 'comments/_ev.fdt' closed at '26353664' before the '37014815' bytes specified in the header were written
com.atlassian.jira.util.RuntimeIOException: java.io.IOException: Entry 'comments/_ev.fdt' closed at '26353664' before the '37014815' bytes specified in the header were written
	at com.atlassian.jira.index.ha.backup.CloseableBackupBuilder.addToBackup(CloseableBackupBuilder.java:72)
	at com.atlassian.jira.index.ha.SnapshotDeletionPolicyContributionStrategy.addToBackup(SnapshotDeletionPolicyContributionStrategy.java:90)
	at com.atlassian.jira.issue.index.DefaultIssueIndexer.contributeToBackup(DefaultIssueIndexer.java:624)
.
.
Caused by: java.io.IOException: Entry 'comments/_ev.fdt' closed at '26353664' before the '37014815' bytes specified in the header were written
  • In the logs we can see that, Jira service tried to create the snapshot in a "temp" path as below.

    /opt/atlassian/jira/temp/snapshot1741759200723/

    2025-03-12 06:00:00,728+0000 Caesium-1-4 INFO anonymous    JIRA Index Snapshot Service [c.a.j.util.compression.ArchiveUtils] Creating archive of type: SNAPPY in path: /opt/atlassian/jira/temp/snapshot1741759200723/IndexSnapshot_11800_250312-060000.tar.sz 
  • However, we observed disc space error for the same path "'The storage device containing the temporary directory '/opt/atlassian/jira/temp' is low on disk space 

    2025-03-12 08:49:13,367+0000 support-zip ERROR      [c.a.t.healthcheck.concurrent.SupportHealthCheckProcess] Health check 'Backup and recovery' failed with severity 'critical': 
    'The storage device containing the temporary directory '/opt/atlassian/jira/temp' is low on disk space (1 GB). This directory is node specific, and lives on its nodes filesystem. 
    Make sure that the amount of free space is double the estimated size of the index ({2}).'

Note- The path above can vary depending on the Jira application installation directory setup.

Cause

The "Jira application installation directory/temp" path where the Jira service first tries to create the snapshot is running low on disk space.

Solution

Review the disk space of the "Jira application installation directory/temp" path. For example, in the above logs above, below path is running low on disk space. If required, increase the disk space.

/opt/atlassian/jira/temp


Last modified on Mar 28, 2025

Was this helpful?

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