Allocation command is malformed; got instead – Elasticsearch Error How To Solve Related Issues



Allocation command is malformed; got instead – 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 “allocation command is malformed; got instead” 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: routing, allocation, cluster.


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”allocation command is malformed; got [{}] instead”classname  is AllocationCommands.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (parser.nextToken() != XContentParser.Token.END_OBJECT) {
  throw new ElasticsearchParseException("allocation command is malformed; done parsing a command;" +
  " but didn't get END_OBJECT; got [{}] instead"; token);
  }
  } else {
  throw new ElasticsearchParseException("allocation command is malformed; got [{}] instead"; token);
  }
  }
  return commands;
  }

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 ElasticSearch: Unassigned Shards, how to fix? -views 222,251 ,score 164

Content-Type header [application/x-www-form-urlencoded] is not supported on Elasticsearch -views   70,656,score 130



Find Configuration Errors

Analyze Now