Malformed – Elasticsearch Error How To Solve Related Issues

Malformed – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch 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 causing many errors 


This guide will help you check for common problems that cause the log “malformed” 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: search, aggregations.

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 discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

Log Context

Log”malformed [“classname  is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (Double.isNaN(lon)) {
  lon = parser.doubleValue();
  } else if (Double.isNaN(lat)) {
  lat = parser.doubleValue();
  } else {
  throw new ParsingException(parser.getTokenLocation(); "malformed [" + ORIGIN_FIELD.getPreferredName()
  + "]: a geo point array must be of the form [lon; lat]");
  return new GeoPoint(lat; lon);

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 BULK API : Malformed action/metadata line [3], expected START_OBJECT but found [VALUE_STRING] -views 11,126 ,score 10

ElasticSearch: ignore_malformed not working -views   2,319,score 3

Find Configuration Errors

Analyze Now