Jira Data Center でクラスタ インデックス レプリケーションのヘルス チェックに失敗
プラットフォームについて: Data Center - この記事は、Data Center プラットフォームのアトラシアン製品に適用されます。
このナレッジベース記事は製品の Data Center バージョン用に作成されています。Data Center 固有ではない機能の Data Center ナレッジベースは、製品のサーバー バージョンでも動作する可能性はありますが、テストは行われていません。サーバー*製品のサポートは 2024 年 2 月 15 日に終了しました。サーバー製品を利用している場合は、アトラシアンのサーバー製品のサポート終了のお知らせページにて移行オプションをご確認ください。
*Fisheye および Crucible は除く
概要
In JIRA Data Center, the search index is replicated amongst other nodes automatically through the shared home. The Cluster Index Replication Health Check will check if the index that is used to provide results of searches for issues is up-to-date on all active nodes in the JIRA Data Center configuration. Each time a change is made in JIRA on a specific node, other nodes will need to be aware of these changes so that search results are up-to-date.
| アイコン | 結果 | 意味 |
|---|---|---|
 | ヘルス チェックは正常に完了しました。 | The health check did not discover any problems with replication. |
 | Index replication for cluster node <node-name> is behind by <seconds> seconds. | The replication is out of date by greater than 2 minutes and less than 5 minutes. This may indicate a performance problem with the environment. |
 | Index replication for cluster node <node-name> is behind by <seconds> seconds. | The replication is out of date by greater than 5 minutes. The replication is either not occurring, or is critically slow. |
トラブルシューティング
| 問題 | 提案 |
|---|---|
| The node(s) can not communicate with the database in a timely manner. | Check that all the nodes are correctly communicating with the database in a timely manner. This can be done by: Verifying the network connection and multicast configuration across your nodes, ensure each node can reach the other within the cluster. Enable SQL query logging in Jira Data Center and verifying if any commands are taking a long time to execute. Test to the disk speed as per Testing Disk Access Speed of the shared home and the $JIRA_HOME on each node. Hook up a profiler to JIRA as per Use jProfiler to analyse Jira application performance during slow performance. If using Apache Web Server as your load balancer, Ensure the jvmRoute parameter is defined for each node, as described in Step 3 of Installing JIRA Data Center. |
| There is unexpected data in the affected table. | Check the contents of the data in the database with the assistance of Atlassian Support. |
| The health check reports nodes to be behind by a number of seconds equal to the timezone offset. | The database server may be in a different timezone to the application servers. See this KB article for details. |
サポートに情報を提供する
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:
- ヘルス チェック結果のスクリーンショット
- Collect a Support ZIP from each of the Data Centre nodes.
- このドキュメントでの提案事項を受けて収集した任意の情報
Additionally, collect the output from the following SQL and provide it with the data above:
SELECT max(id), node_id FROM replicatedindexoperation GROUP BY node_id;
SELECT * FROM nodeindexcounter;