Health check: OpenSearch Mappings Limit in Jira Data Center

プラットフォームについて: Data Center のみ。 - This article only applies to Atlassian apps on the Data Center プラットフォーム

この KB は Data Center バージョンの製品用に作成されています。Data Center 固有ではない機能の Data Center KB は、製品のサーバー バージョンでも動作する可能性はありますが、テストは行われていません。 Server* 製品のサポートは 2024 年 2 月 15 日に終了しました。Server 製品を実行している場合は、 アトラシアン Server サポート終了 のお知らせにアクセスして、移行オプションを確認してください。

*Fisheye および Crucible は除く

要約

In OpenSearch, mappings define how documents and their fields are stored and indexed. Each field in Jira, whether a system field or a custom field, is mapped as an index field to enable search functionality. As you create more custom fields in Jira, the size of these mappings can grow, which might impact the performance and memory usage of your OpenSearch cluster.

OpenSearch provides several settings to help maintain cluster performance and prevent memory issues caused by creating an excessive number of fields. One such setting is index.mapping.total_fields.limit, which sets the maximum number of fields allowed in an OpenSearch index (the default is 1000).

This health check verifies if the current number of fields is approaching this limit.

ソリューション

Understand the Health Check results

アイコン

結果

意味

The OpenSearch index has <mappings-count>field mappings, which is <percent>% of the maximum limit of <limit>.

The current limit is sufficiently high.

⚠️

The OpenSearch index has <mappings-count>field mappings, which is <percent>% of the maximum limit of <limit>. We recommend increasing the limit for the OpenSearch index.

The number of fields is approaching the index.mapping.total_fields.limit setting on your index. This means, it’s 80% or more.

The OpenSearch index has reached its field mapping limit (<limit>). New fields won't be indexed or appear in search results. We recommend increasing the field mapping limit.

The index.mapping.total_fields.limit setting has been reached.

⚠️

Unable to assess the OpenSearch index mappings or limit.

There was a problem checking the OpenSearch index mappings or settings.

トラブルシューティング

問題

提案

The number of fields is approaching the mappings limit

Increase the index.mapping.total_fields.limit on your OpenSearch index. More about mappings

Use an index template to make sure that this setting is applied permanently, even after you rebuild the index. For more details, see Configuring index settings on OpenSearch.

Please note: Increasing this limit requires careful consideration of cluster resources.

Note that once a field is created in OpenSearch mappings, it can’t be deleted. To clean up stale mappings, you need to perform a re-index. Explore how to re-index Jira

The index.mapping.total_fields.limit setting has been reached

Increase the index.mapping.total_fields.limit on your OpenSearch index. More about mappings

Use an index template to make sure that this setting will be applied permanently, even after you rebuild the index. For more details, see Configuring index settings on OpenSearch.

Please note: Increasing this limit requires careful consideration of cluster resources.

Some fields might have failed to be created due to hitting this limit. You can verify this by checking the Missing OpenSearch Mappings health check. In such case, perform a re-index after increasing the fields limit. Explore how to re-index Jira

There was a problem checking the OpenSearch index

Check logs for errors. Some possible reasons are network connectivity issues or lack of permissions. For more details, see Securing an OpenSearch cluster.

更新日時: November 5, 2025

さらにヘルプが必要ですか?

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