[data.search] Stop sending entire request body in polling requests #186138
Labels
Feature:Search
Querying infrastructure in Kibana
impact:medium
Addressing this issue will have a medium level of impact on the quality/strength of our product.
loe:medium
Medium Level of Effort
performance
Project:AsyncSearch
Background search, partial results, async search services.
Team:DataDiscovery
Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL.
Summary:
Currently, when using the
data.search
services, we are sending the entire search request body to every polling request. This takes up a lot of data transfer and is unnecessary, since all we're using is the search request ID to poll on the ES_async_status
endpoint.We should check and make sure that other search strategies aren't negatively affected if we switch over to just sending the request ID, and we should also make sure that things like "other bucket" scenarios still work.
Consider, for example, these requests:
This shows three distinct async search requests. The final responses are indicated by the larger
response_length
. It is totally unnecessary to be sending such a large request body (indicated byrequest_length
) in each of the polls leading up to the final response.The text was updated successfully, but these errors were encountered: