Health check: Storage index snapshot

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。

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.

*Fisheye および Crucible は除く

概要

To keep a copy of the recent state of the index, Jira creates a search index snapshot. This helps ensure that in a failover scenario, the node that takes over from the failed node can quickly acquire the most recent possible index without the need for a full re-indexing operation. The index snapshot storage health check verifies the snapshot storage configuration for problems that may prevent the backup and recovery of the search index.


ヘルス チェック結果 

アイコン結果意味

All checks have passed successfully.

No storage issues for the index snapshot have been detected.

Couldn’t calculate the amount of required free space because the index snapshot directory (<directory>) doesn't exist.

There was a problem with accessing or locating the reported directory.

The storage device containing the temporary directory (<directory>) is low on disk space (<remaining_size> left). Make sure that the amount of free space is double the estimated size of the index (<estimated_index_size>).

There isn’t enough disk space available in the reported directory.

The storage device containing the snapshot directory (<directory>) is low on disk space (<remaining_size> left). Make sure that the amount of free space is double the estimated size of the index snapshot (<estimated_index_size>).

There isn’t enough disk space available in the reported directory.

Jira can’t write to the snapshot directory (<directory>). Check directory access permissions.

Jira was unable to create an empty file in the snapshot directory. Creating an index snapshot may also fail.

The name of the file Jira creates for the purpose of this check follows the convention of IndexSnapshotFileSystemUtil
_testFile_<time_in_ms>
_<node_id>
. The file should be automatically deleted after the health check is complete. If it’s not, you can safely delete it manually.

ソリューション

Here’s what you can do depending on the reason why the health check has failed in your system:

Couldn’t calculate the amount of required disk space

Ensure that Jira has permission to read from and write to the snapshot directory.

The storage device is low on disk space

The available storage space in the reported directory is lower than the required amount. Make sure that the amount of free disk space is at least twice the size of your current working index. You should also allow for the growth of the index over time.

Jira can’t write to the snapshot directory

Ensure that Jira has permission to write to the snapshot directory.

Lucene search is not available

Contact Atlassian Support providing the information listed in “Requesting support”.


サポートに情報を提供する

トラブルシューティングやご自身での問題の解決が難しい場合、support.atlassian.com でサポート チケットを作成し、次の情報を含めてください。

  • ヘルス チェック結果のスクリーンショット
  • 各 Data Center ノードからのサポート zip
  • このドキュメントでの提案事項を受けて収集した任意の情報


In the event that the directory is reported as missing but does exist on the file system: 

影響を受けているファイルのシステム ロケーション [directory] の詳細を、所有者がわかる状態で提供してください。これは次のステップで行えます。
  • Linux

    ls -lahR [directory] | gzip -9 > fileListing.gz
  • Windows

    Microsoft の AccessEnum SysInternals ツールを使用してタスクを完了し、使用されている共有ディレクトリの権限を表示した状態のスクリーンショットを取得します。


最終更新日: 2023 年 10 月 3 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.