Getting shared home health check error when using Azure Blob Storage
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
After changing to Azure Blob storage for the Jira Shared Home Directory, the following error is received in the Health Check
Name: Shared Home
Is healthy: false
Failure reason: ["Node node2 is not actively using shared home /datashare/application-data/jira. Last update was 151,151 seconds ago.","Node node3 is not actively using shared home /datashare/application-data/jira. Last update was 150,612 seconds ago.","Node node4 is not actively using shared home /datashare/application-data/jira. Last update was 148,408 seconds ago."]
Severity: CRITICALEnvironment
Jira DataCenter deployed on Azure
Cause
Even with the following setup correct:
- Shared Home path is correctly configured in cluster.properties files;
- Shared Home is mounted in all nodes;
- All nodes can write to Shared Home volume
On creating a file in shared home in one node it will be available only to other nodes after a few minutes;
Azure Blob Storage has a delay in making data available to all nodes.
Solution
Use Azure File Storage (SMB) for Shared Home path instead.
Atlassian has not specifically tested with Blob Storage, therefore we cannot guarantee that it works. Please see Getting started with Jira Data Center on Azure for what environment we have used for the provided templates.