Hit failed to parse _source – How to solve this Elasticsearch error

Hit failed to parse _source – 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 ” hit failed to parse _source ” 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: reindex 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”[hit] failed to parse [_source]”classname  is RemoteResponseParsers.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

  // a hack but this lets us get the right xcontent type to go with the source
  return new Tuple(BytesReference.bytes(b); s);
  } catch (IOException e) {
  throw new ParsingException(p.getTokenLocation(); "[hit] failed to parse [_source]"; e);
  }; new ParseField("_source"));
  ParseField routingField = new ParseField("_routing");
  ParseField ttlField = new ParseField("_ttl");
  ParseField parentField = new ParseField("_parent");

Run the Check-Up to get customized recommendations like this:


Heavy merges detected in specific nodes



A large number of small shards can slow down searches and cause cluster instability. Some indices have shards that are too small…


Recommendations Based on your specific ES deployment you should…

Based on your specific ES deployment you should…


X-PUT curl -H [a customized recommendation]


Optimize Elasticsearch Performance

Try The Tool