+ NAME + analyzer ” + analyzer + ” not found – How to solve this Elasticsearch error

Average Read Time

2 Mins

+ NAME + analyzer ” + analyzer + ” not found – 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 ” + NAME + analyzer ” + analyzer + ” not found ” 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: query and 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”[” + NAME + “] analyzer [” + analyzer + “] not found”classname  is MatchBoolPrefixQueryBuilder.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

  protected Query doToQuery(QueryShardContext context) throws IOException {
  if (analyzer != null && context.getIndexAnalyzers().get(analyzer) == null) {
  throw new QueryShardException(context; "[" + NAME + "] analyzer [" + analyzer + "] not found");
  final MatchQuery matchQuery = new MatchQuery(context);
  if (analyzer != null) {


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

Analyze your cluster