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

Allocation command is malformed; got instead – 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 Error 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; 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 and 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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (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;
  }

 

Run the Check-Up to get a customized report like this:

Analyze your cluster