Jira サーバーでクラスタ キャッシュ レプリケーションのヘルス チェックに失敗
This Knowledge Base article was written specifically for Atlassian Data Center applications. The contents of this article do not apply to Server installations or the Atlassian Cloud platform.
JIRA Data Center cluster replication relies on nodes being recorded in a database and also receiving and sending updates. The Health Check confirms that the replication is working in the entire cluster. If an active node is not responding, the other nodes are going to be reporting warnings and the one with the error will report a critical result.
Understanding the Results
|アイコン||結果||What this means|
|The health check passed successfully.||Node replication within the cluster is working.|
|The node |
The node does not appear to be in the database however does exist within the replication cache, or the node is unresponsive.
|The node ||The node is not replicating information to the cluster - it exists in the database but not the replication cache.|
|The node is not in the database.|
Restart the affected node. Prior to doing so, it is recommended to collect some thread dumps as per Generating a Thread Dump as these can be sent to support with the data below.
|The node is not replicating due to a network condition.|
|The node is not replicating due to nodes being offline.||Check the status of each of the other nodes, specifically if they are online and responsive.|
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.