Max shingle size must be at least MAX SHINGLE SIZE LOWER BOUND and at most – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.2-7.9

Briefly, this error occurs when the ‘max_shingle_size’ parameter in Elasticsearch is set outside the allowed range. The ‘max_shingle_size’ parameter is used in the shingle token filter to control the maximum shingle size. To resolve this issue, you should adjust the ‘max_shingle_size’ parameter to a value within the allowed range. This range is defined by the constants ‘MAX_SHINGLE_SIZE_LOWER_BOUND’ and ‘MAX_SHINGLE_SIZE_UPPER_BOUND’. If you’re unsure of the appropriate value, consider using the default value or consult the Elasticsearch documentation for guidance.

This guide will help you check for common problems that cause the log ” [max_shingle_size] must be at least [” + MAX_SHINGLE_SIZE_LOWER_BOUND + “] and at most ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index.

Log Context

Log “[max_shingle_size] must be at least [” + MAX_SHINGLE_SIZE_LOWER_BOUND + “] and at most ” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 this.similarity = similarity;
 }  public Builder maxShingleSize(int maxShingleSize) {
 throw new MapperParsingException("[max_shingle_size] must be at least [" + MAX_SHINGLE_SIZE_LOWER_BOUND + "] and at most " +
 "[" + MAX_SHINGLE_SIZE_UPPER_BOUND + "]; got [" + maxShingleSize + "]");
 this.maxShingleSize = maxShingleSize;
 return builder;


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?