Max_shingle_size must be at least ” + MAX_SHINGLE_SIZE_LOWER_BOUND + ” and at most – How to solve this Elasticsearch error

Max_shingle_size must be at least ” + MAX_SHINGLE_SIZE_LOWER_BOUND + ” and at most – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues that cause many errors.

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. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: index.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

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

this.similarity = similarity;
  }
 
  public Builder maxShingleSize(int maxShingleSize) {
  if (maxShingleSize  MAX_SHINGLE_SIZE_UPPER_BOUND) {
  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;
  }

 

Run the Check-Up to get a customized report like this:

Analyze your cluster