2018-10-25 11:59:59 -04:00
|
|
|
[[search-settings]]
|
2020-06-01 09:44:32 -04:00
|
|
|
=== Search settings
|
2018-10-25 11:59:59 -04:00
|
|
|
|
2020-05-11 09:45:09 -04:00
|
|
|
The following expert settings can be set to manage global search and aggregation
|
|
|
|
|
limits.
|
2018-10-25 11:59:59 -04:00
|
|
|
|
2019-05-13 08:42:26 -04:00
|
|
|
[[indices-query-bool-max-clause-count]]
|
2018-10-25 11:59:59 -04:00
|
|
|
`indices.query.bool.max_clause_count`::
|
2020-05-12 16:25:41 -04:00
|
|
|
(integer)
|
2020-05-11 09:45:09 -04:00
|
|
|
Maximum number of clauses a Lucene BooleanQuery can contain. Defaults to `1024`.
|
|
|
|
|
+
|
2018-10-25 11:59:59 -04:00
|
|
|
This setting limits the number of clauses a Lucene BooleanQuery can have. The
|
|
|
|
|
default of 1024 is quite high and should normally be sufficient. This limit does
|
|
|
|
|
not only affect Elasticsearchs `bool` query, but many other queries are rewritten to Lucene's
|
2019-06-10 05:12:22 -04:00
|
|
|
BooleanQuery internally. The limit is in place to prevent searches from becoming too large
|
|
|
|
|
and taking up too much CPU and memory. In case you're considering increasing this setting,
|
|
|
|
|
make sure you've exhausted all other options to avoid having to do this. Higher values can lead
|
2018-10-25 11:59:59 -04:00
|
|
|
to performance degradations and memory issues, especially in clusters with a high load or
|
|
|
|
|
few resources.
|
2020-05-11 09:45:09 -04:00
|
|
|
|
|
|
|
|
[[search-settings-max-buckets]]
|
|
|
|
|
`search.max_buckets`::
|
|
|
|
|
(<<cluster-update-settings,Dynamic>>, integer)
|
|
|
|
|
Maximum number of <<search-aggregations-bucket,aggregation buckets>> allowed in
|
|
|
|
|
a single response. Defaults to `10000`.
|
|
|
|
|
+
|
|
|
|
|
Requests that attempt to return more than this limit will return an error.
|
