Allocation command is malformed; done parsing a command; – Elasticsearch Error How To Solve Related Issues



Allocation command is malformed; done parsing a command; – 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; done parsing a command;” 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; done parsing a command;”classname  is AllocationCommands.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

String commandName = parser.currentName();
  token = parser.nextToken();
  commands.add(parser.namedObject(AllocationCommand.class; commandName; null));
  // move to the end object one
  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);
  }

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 SyntaxError: unexpected EOF while parsing -views 408,593 ,score 42

JsonMappingException: out of START_ARRAY token -views   306,037,score 101



Find Configuration Errors

Analyze Now