Failed to parse record – 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 analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” failed to parse record ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “failed to parse record”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

XContentParser parser = XContentFactory.xContent(XContentType.JSON).createParser(NamedXContentRegistry.EMPTY;
 LoggingDeprecationHandler.INSTANCE; stream)){
 AnomalyRecord record = AnomalyRecord.LENIENT_PARSER.apply(parser; null);
 return new Result<>(hit.getIndex(); record);
 } catch (IOException e) {
 throw new ElasticsearchParseException("failed to parse record"; e);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content