-
Notifications
You must be signed in to change notification settings - Fork 25.8k
How to simulate long running search requests #54159
Copy link
Copy link
Closed
Labels
:Delivery/BuildBuild or test infrastructureBuild or test infrastructure:Search/SearchSearch-related issues that do not fall into other categoriesSearch-related issues that do not fall into other categories>featureTeam:DeliveryMeta label for Delivery teamMeta label for Delivery teamTeam:SearchMeta label for search teamMeta label for search team
Metadata
Metadata
Assignees
Labels
:Delivery/BuildBuild or test infrastructureBuild or test infrastructure:Search/SearchSearch-related issues that do not fall into other categoriesSearch-related issues that do not fall into other categories>featureTeam:DeliveryMeta label for Delivery teamMeta label for Delivery teamTeam:SearchMeta label for search teamMeta label for search team
Type
Fields
Give feedbackNo fields configured for issues without a type.
For the development of the
async_searchAPIs we needed a way to simulate long running queries. For this purpose we wrote a small module that can simulate such long running queries on shards. We used it for demo and monkey testing but we've also shared it with Kibana to help them integrating the new feature. While sharing a plugin/module is ok when developing a feature in master, we think that this module could be used outside of the development phase by other solutions to simulate long running queries.A question was raised whether we want to provide this plugin/module in our distribution automatically in order to let users play with long running queries without requiring to index billions of documents.
The way we simulate long running queries can be discussed in a follow up, the current module uses
Thread.sleepbut it's an implementation details at this point. I opened this issue to discuss two points:Does that sound useful to provide a way for users to simulate long running queries easily in Elasticsearch.
If so, how should we expose such functionality.
We probably don't want this module to be available in production deployment so @jasontedor proposed that we ship the module automatically in the distribution only if the build is a snapshot build.
Another option would be to provide such functionalities as an example plugin only available in our build.