A query cannot be repeated more than 100 times found – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.16-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when a query is repeated more than 100 times in Elasticsearch. This is a built-in limit to prevent excessive resource usage. To resolve this issue, you can optimize your queries to avoid repetition. If the repetition is necessary, consider breaking down your query into smaller parts or using a different approach to retrieve the data. You could also increase the limit, but this should be done with caution as it may impact performance.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” A query cannot be repeated more than 100 times; found [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: parser, plugin, query.

Log Context

Log “A query cannot be repeated more than 100 times; found [{}]” class name is LogicalPlanBuilder.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 long value = number.longValue();
 if (value < 1) {
 throw new ParsingException(source(numberCtx); "A positive runs value is required; found [{}]"; value);
 if (value > 100) {
 throw new ParsingException(source(numberCtx); "A query cannot be repeated more than 100 times; found [{}]"; value);
 runs = (int) value;
 }  int numberOfQueries = queries.size() + runs;


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?