Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update docs for new clause count setting #7391

Merged
merged 8 commits into from
Jul 1, 2024
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,8 @@

- `indices.fielddata.cache.size` (String): The maximum size of the field data cache. May be specified as an absolute value (for example, `8GB`) or a percentage of the node heap (for example, `50%`). This value is static so you must specify it in the `opensearch.yml` file. If you don't specify this setting, the maximum size is unlimited. This value should be smaller than the `indices.breaker.fielddata.limit`. For more information, see [Field data circuit breaker]({{site.url}}{{site.baseurl}}/install-and-configure/configuring-opensearch/circuit-breaker/#field-data-circuit-breaker-settings).

- `indices.query.bool.max_clause_count` (Integer): Defines the maximum value for the product of the number of fields and the number of terms that can be queried at one time. Default value is 1024. Note that prior to OpenSearch versions 2.16, this was a static setting that required a cluster restart to take effect. Due to the nature of changing a static setting to being dynamic, it is possible that search threadpools hold the older static value before the dynamic setting is applied on all nodes thereby causing certain search requests to still error out with `TooManyClauses` exception. When new search threadpools are created, they will hold a reference to the new value.

Check failure on line 42 in _install-and-configure/configuring-opensearch/index-settings.md

View workflow job for this annotation

GitHub Actions / style-job

[vale] reported by reviewdog 🐶 [OpenSearch.Spelling] Error: threadpools. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks. Raw Output: {"message": "[OpenSearch.Spelling] Error: threadpools. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.", "location": {"path": "_install-and-configure/configuring-opensearch/index-settings.md", "range": {"start": {"line": 42, "column": 409}}}, "severity": "ERROR"}

Check failure on line 42 in _install-and-configure/configuring-opensearch/index-settings.md

View workflow job for this annotation

GitHub Actions / style-job

[vale] reported by reviewdog 🐶 [OpenSearch.Spelling] Error: threadpools. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks. Raw Output: {"message": "[OpenSearch.Spelling] Error: threadpools. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.", "location": {"path": "_install-and-configure/configuring-opensearch/index-settings.md", "range": {"start": {"line": 42, "column": 608}}}, "severity": "ERROR"}
vagimeli marked this conversation as resolved.
Show resolved Hide resolved

- `cluster.remote_store.index.path.type` (String): The path strategy for the data stored in the remote store. This setting is effective only for remote-store-enabled clusters. This setting supports the following values:
- `fixed`: Stores the data in path structure `<repository_base_path>/<index_uuid>/<shard_id>/`.
- `hashed_prefix`: Stores the data in path structure `hash(<shard-data-idenitifer>)/<repository_base_path>/<index_uuid>/<shard_id>/`.
Expand Down
Loading