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.

Sign up for GitHub

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

[Docs] Add indices.query.bool.max_clause_count setting #34779

Merged
merged 1 commit into from
Oct 25, 2018
Merged

[Docs] Add indices.query.bool.max_clause_count setting #34779

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs/reference/modules/indices.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,10 @@ Available settings include:

Control the resource limits on the shard recovery process.

<<search-settings,Search Settings>>::

Control global search settings.

include::indices/circuit_breaker.asciidoc[]

include::indices/fielddata.asciidoc[]
Expand All @@ -42,3 +46,5 @@ include::indices/request_cache.asciidoc[]

include::indices/recovery.asciidoc[]

include::indices/search-settings.asciidoc[]

16 changes: 16 additions & 0 deletions docs/reference/modules/indices/search-settings.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
[[search-settings]]
=== Search Settings

The following _expert_ setting can be set to manage global search limits.

`indices.query.bool.max_clause_count`::
Defaults to `1024`.

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
BooleanQuery internally. The limit is in place to prevent searches from becoming to large
and taking up too much CPU and memory. In case you consider to increase this setting,
make sure you exhausted all other options to avoid having to do this. Higher values can lead
to performance degradations and memory issues, especially in clusters with a high load or
few resources.