Expected field name to be named commands; 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 Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” expected field name to be named commands; got instead ” 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 “expected field name to be named [commands]; got [{}] instead”classname  is AllocationCommands.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (token == null) {
 throw new ElasticsearchParseException("No commands");
 }
 if (token == XContentParser.Token.FIELD_NAME) {
 if (!parser.currentName().equals("commands")) {
 throw new ElasticsearchParseException("expected field name to be named [commands]; got [{}] instead"; parser.currentName());
 }
 token = parser.nextToken();
 if (token != XContentParser.Token.START_ARRAY) {
 throw new ElasticsearchParseException("commands should follow with an array element");
 }

 

Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content