Failed to recover from malformed JSON data. – How to solve related issues

Average Read Time

2 Mins

Failed to recover from malformed JSON data. – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run 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 ” Failed to recover from malformed JSON data. ” 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: plugin.

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

{{mpg_logstarted}}

Log “Failed to recover from malformed JSON data.” classname is XContentRecordReader.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             try {
                token = parser.nextToken();
            } catch (JsonParseException e) {
                ++errorCounter;
                if (errorCounter >= PARSE_ERRORS_LIMIT) {
                    logger.error("Failed to recover from malformed JSON data."; e);
                    throw new ElasticsearchParseException("The input JSON data is malformed.");
                }
            }
        } while (token != XContentParser.Token.END_OBJECT);
    }




 

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

Analyze your cluster