Allocation command is malformed; done parsing a command; – How to solve this Elasticsearch error

Average Read Time

2 Mins

Allocation command is malformed; done parsing a command; – 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 Check-Up which can resolve issues that cause 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. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: routing, allocation and cluster.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

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);
 }

 

Watch a demo of the Check-Up:

Analyze your cluster