From 59035238396eaef85f4ed20e96cc1c69d83f33c4 Mon Sep 17 00:00:00 2001 From: Harsha Vamsi Kalluri Date: Fri, 14 Jun 2024 09:22:47 -0700 Subject: [PATCH 1/6] Update docs for new clause count setting Signed-off-by: Harsha Vamsi Kalluri --- _install-and-configure/configuring-opensearch/index-settings.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/_install-and-configure/configuring-opensearch/index-settings.md b/_install-and-configure/configuring-opensearch/index-settings.md index 543fa92b0d..562e51b18a 100644 --- a/_install-and-configure/configuring-opensearch/index-settings.md +++ b/_install-and-configure/configuring-opensearch/index-settings.md @@ -39,6 +39,8 @@ OpenSearch supports the following cluster-level index settings. All settings in - `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.15, 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. + - `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 `///`. - `hashed_prefix`: Stores the data in path structure `hash()////`. From 17003ff17ec849214599f5e423f530fa6a3c3a68 Mon Sep 17 00:00:00 2001 From: Harsha Vamsi Kalluri Date: Fri, 14 Jun 2024 09:24:26 -0700 Subject: [PATCH 2/6] Update to 2.16 Signed-off-by: Harsha Vamsi Kalluri --- _install-and-configure/configuring-opensearch/index-settings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_install-and-configure/configuring-opensearch/index-settings.md b/_install-and-configure/configuring-opensearch/index-settings.md index 562e51b18a..39e5019502 100644 --- a/_install-and-configure/configuring-opensearch/index-settings.md +++ b/_install-and-configure/configuring-opensearch/index-settings.md @@ -39,7 +39,7 @@ OpenSearch supports the following cluster-level index settings. All settings in - `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.15, 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. +- `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. - `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 `///`. From 2a152fd29fdeba531842e03526ad8ce06dc2e1f1 Mon Sep 17 00:00:00 2001 From: Melissa Vagi Date: Fri, 28 Jun 2024 12:13:06 -0600 Subject: [PATCH 3/6] Update _install-and-configure/configuring-opensearch/index-settings.md Signed-off-by: Melissa Vagi --- _install-and-configure/configuring-opensearch/index-settings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_install-and-configure/configuring-opensearch/index-settings.md b/_install-and-configure/configuring-opensearch/index-settings.md index 39e5019502..77dfc3fa04 100644 --- a/_install-and-configure/configuring-opensearch/index-settings.md +++ b/_install-and-configure/configuring-opensearch/index-settings.md @@ -39,7 +39,7 @@ OpenSearch supports the following cluster-level index settings. All settings in - `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. +- `indices.query.bool.max_clause_count` (Integer): Defines the maximum product of fields and terms queryable at once. Before OpenSearch 2.16, this static setting required a cluster restart to apply. Now dynamic, existing search thread pools may use the old static value initially, causing `TooManyClauses` exceptions. New thread pools use the updated value. Default is 1024. - `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 `///`. From 991f2256a899e5944642c40bb9837536fa800f8c Mon Sep 17 00:00:00 2001 From: Melissa Vagi Date: Fri, 28 Jun 2024 12:15:18 -0600 Subject: [PATCH 4/6] Update _install-and-configure/configuring-opensearch/index-settings.md Signed-off-by: Melissa Vagi --- _install-and-configure/configuring-opensearch/index-settings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_install-and-configure/configuring-opensearch/index-settings.md b/_install-and-configure/configuring-opensearch/index-settings.md index 77dfc3fa04..def4925128 100644 --- a/_install-and-configure/configuring-opensearch/index-settings.md +++ b/_install-and-configure/configuring-opensearch/index-settings.md @@ -39,7 +39,7 @@ OpenSearch supports the following cluster-level index settings. All settings in - `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 product of fields and terms queryable at once. Before OpenSearch 2.16, this static setting required a cluster restart to apply. Now dynamic, existing search thread pools may use the old static value initially, causing `TooManyClauses` exceptions. New thread pools use the updated value. Default is 1024. +- `indices.query.bool.max_clause_count` (Integer): Defines the maximum product of fields and terms queryable at once. Before OpenSearch 2.16, this static setting required a cluster restart to apply. Now dynamic, existing search thread pools may use the old static value initially, causing `TooManyClauses` exceptions. New thread pools use the updated value. Default is `1024`. - `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 `///`. From d32b4e4a7b2c422231e20e33ab9f0e7b2b41e5d8 Mon Sep 17 00:00:00 2001 From: Melissa Vagi Date: Mon, 1 Jul 2024 10:12:35 -0600 Subject: [PATCH 5/6] Update _install-and-configure/configuring-opensearch/index-settings.md Co-authored-by: Nathan Bower Signed-off-by: Melissa Vagi --- _install-and-configure/configuring-opensearch/index-settings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_install-and-configure/configuring-opensearch/index-settings.md b/_install-and-configure/configuring-opensearch/index-settings.md index def4925128..377c577f6d 100644 --- a/_install-and-configure/configuring-opensearch/index-settings.md +++ b/_install-and-configure/configuring-opensearch/index-settings.md @@ -39,7 +39,7 @@ OpenSearch supports the following cluster-level index settings. All settings in - `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 product of fields and terms queryable at once. Before OpenSearch 2.16, this static setting required a cluster restart to apply. Now dynamic, existing search thread pools may use the old static value initially, causing `TooManyClauses` exceptions. New thread pools use the updated value. Default is `1024`. +- `indices.query.bool.max_clause_count` (Integer): Defines the maximum product of fields and terms that are queryable at once. Before OpenSearch 2.16, a cluster restart was required in order to apply this static setting. Now dynamic, existing search thread pools may use the old static value initially, causing `TooManyClauses` exceptions. New thread pools use the updated value. Default is `1024`. - `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 `///`. From 7dc8c425af6ad1f0b1682ee3864070f0fa3ab095 Mon Sep 17 00:00:00 2001 From: Melissa Vagi Date: Mon, 1 Jul 2024 10:13:40 -0600 Subject: [PATCH 6/6] Update _install-and-configure/configuring-opensearch/index-settings.md Signed-off-by: Melissa Vagi --- _install-and-configure/configuring-opensearch/index-settings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_install-and-configure/configuring-opensearch/index-settings.md b/_install-and-configure/configuring-opensearch/index-settings.md index 377c577f6d..1cade229be 100644 --- a/_install-and-configure/configuring-opensearch/index-settings.md +++ b/_install-and-configure/configuring-opensearch/index-settings.md @@ -39,7 +39,7 @@ OpenSearch supports the following cluster-level index settings. All settings in - `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 product of fields and terms that are queryable at once. Before OpenSearch 2.16, a cluster restart was required in order to apply this static setting. Now dynamic, existing search thread pools may use the old static value initially, causing `TooManyClauses` exceptions. New thread pools use the updated value. Default is `1024`. +- `indices.query.bool.max_clause_count` (Integer): Defines the maximum product of fields and terms that are queryable simultaneously. Before OpenSearch 2.16, a cluster restart was required in order to apply this static setting. Now dynamic, existing search thread pools may use the old static value initially, causing `TooManyClauses` exceptions. New thread pools use the updated value. Default is `1024`. - `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 `///`.