3b96055b23
By default the number of searches msearch executes is capped by the number of nodes multiplied with the default size of the search threadpool. This default can be overwritten by using the newly added `max_concurrent_searches` parameter. Before the msearch api would concurrently execute all searches concurrently. If many large msearch requests would be executed this could lead to some searches being rejected while other searches in the msearch request would succeed. The goal of this change is to avoid this exhausting of the search TP. Closes #17926 |
||
|---|---|---|
| .. | ||
| request | ||
| suggesters | ||
| count.asciidoc | ||
| explain.asciidoc | ||
| field-stats.asciidoc | ||
| multi-search.asciidoc | ||
| percolate.asciidoc | ||
| profile.asciidoc | ||
| request-body.asciidoc | ||
| search-shards.asciidoc | ||
| search-template.asciidoc | ||
| search.asciidoc | ||
| suggesters.asciidoc | ||
| uri-request.asciidoc | ||
| validate.asciidoc | ||