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

[8.0] Configure IndexSearcher.maxClauseCount() based on Node characteristics (#81525) #81850

Merged
merged 1 commit into from
Dec 17, 2021

Conversation

romseygeek
Copy link
Contributor

Backports the following commits to 8.0:

elastic#81525)

This commit deprecates the indices.query.bool.max_clause_count node setting,
and instead configures the maximum clause count for lucene based on the available
heap and the size of the thread pool.

Closes elastic#46433
@romseygeek romseygeek added auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport labels Dec 17, 2021
@romseygeek
Copy link
Contributor Author

@elasticmachine run elasticsearch-ci/part-2

@elasticsearchmachine elasticsearchmachine merged commit 9f68c08 into elastic:8.0 Dec 17, 2021
@romseygeek romseygeek deleted the backport/8.0/pr-81525 branch December 20, 2021 13:41
romseygeek added a commit that referenced this pull request Jan 20, 2022
This check issues a warning if the cluster contains an index that has more
than 1024 fields, and no default_field set for searching. However, the 1024
boolean clause limit is no longer relevant with #81850, and in any case this
isn't something that would have prevented a successful upgrade from 7.17 to
8.0, so we can remove the check entirely.

Fixes #81539
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport v8.0.0-rc1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants