Allocation command is malformed got instead – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when the Elasticsearch cluster receives an incorrectly formatted allocation command. The command is expected to have certain parameters, but instead, it received an empty object [{}]. To resolve this issue, you should review the syntax of your allocation command. Ensure that it includes all necessary parameters and that they are correctly formatted. If you’re using a script or application to send the command, check that it’s correctly generating the command.

This guide will help you check for common problems that cause the log ” allocation command is malformed; got [{}] instead ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: routing, allocation, cluster.

Log Context

Log “allocation command is malformed; got [{}] instead” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 "allocation command is malformed; done parsing a command;" + " but didn't get END_OBJECT; got [{}] instead";
 } else {
 throw new ElasticsearchParseException("allocation command is malformed; got [{}] instead"; token);
 return commands;