-
Notifications
You must be signed in to change notification settings - Fork 24.7k
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
Add circuit breaker to QueryStringQueryParser #51403
Labels
>enhancement
:Search Relevance/Search
Catch all for Search Relevance
Team:Search Relevance
Meta label for the Search Relevance team in Elasticsearch
Comments
romseygeek
added
:Search/Search
Search-related issues that do not fall into other categories
:Core/Infra/Circuit Breakers
Track estimates of memory consumption to prevent overload
labels
Jan 24, 2020
Pinging @elastic/es-core-infra (:Core/Infra/Circuit Breakers) |
Pinging @elastic/es-search (:Search/Search) |
rjernst
added
Team:Core/Infra
Meta label for core/infra team
Team:Search
Meta label for search team
labels
May 4, 2020
romseygeek
removed
:Core/Infra/Circuit Breakers
Track estimates of memory consumption to prevent overload
Team:Core/Infra
Meta label for core/infra team
needs:triage
Requires assignment of a team area label
labels
Dec 15, 2020
Pinging @elastic/es-search (Team:Search) |
benwtrent
added
:Search Relevance/Search
Catch all for Search Relevance
and removed
:Search/Search
Search-related issues that do not fall into other categories
labels
Jul 12, 2024
elasticsearchmachine
added
Team:Search Relevance
Meta label for the Search Relevance team in Elasticsearch
and removed
Team:Search
Meta label for search team
labels
Jul 12, 2024
Pinging @elastic/es-search-relevance (Team:Search Relevance) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
>enhancement
:Search Relevance/Search
Catch all for Search Relevance
Team:Search Relevance
Meta label for the Search Relevance team in Elasticsearch
The QueryStringQueryParser can produce extremely large queries that don't get caught quickly enough by our boolean query limit checks - for example, a string that contains large numbers of spaces and wildcards can produce lots of very heavy Wildcard or Prefix queries over multiple fields. We should add some query-construction time checks to ensure that these sort of heavy queries don't overwhelm a node before they've even had time to run.
The text was updated successfully, but these errors were encountered: