Resolving Issue with Low Disk Space on Jira Temporary Directory Running on Kubernetes
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
Summary
While running Jira on Kubernetes, a low disk space warning for the temporary directory /opt/atlassian/jira/temp may occur. The specific error message is:
1
Low disk space on device containing temporary directory (/opt/atlassian/jira/temp) - xx GB of free space remaining. Index backup and recovery may fail.Symptoms
You receive a health check notification indicating low disk space on the device containing the Jira temporary directory /opt/atlassian/jira/temp. Index backup and recovery may fail due to insufficient disk space.
Environment
Jira on Kubernetes
Cause
The default storage provision for the Jira temporary directory may not be sufficient for your usage.
Solution
Mounting an additional volume for the temporary directory in Jira running on Kubernetes can resolve the low disk space issue, ensuring that index backup and recovery operations can proceed without any failures. We can mount an additional volume for the temporary directory. To address this, you can mount an additional volume for the temporary directory. You may use an existing suitable persistent volume or create a new one according to your environment. In this example, we will use the existing local-home persistent volume with an additional subpath value. Follow these steps:
Open the Jira Helm Chart configuration file (values.yaml) used for deploying Jira on Kubernetes.
Add the additionalVolumeMounts configuration to the Helm Chart values file to mount a specific volume to the temporary directory.
Here is an example configuration snippet:
1 2 3 4additionalVolumeMounts: - mountPath: /opt/atlassian/jira/temp subPath: temp name: local-homeApply the configuration and redeploy the Jira Helm Chart. Details on updating the helm installation can be found on https://atlassian.github.io/data-center-helm-charts/userguide/upgrades/PRODUCTS_UPGRADE/.
Here is an example output after the fix:
Was this helpful?