Expected either field name commands; or start array; 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 either field name commands; or start array; 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 either field name [commands]; or start array; got [{}] instead”classname  is AllocationCommands.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

throw new ElasticsearchParseException("commands should follow with an array element");
 }
 } else if (token == XContentParser.Token.START_ARRAY) {
 // ok...
 } else {
 throw new ElasticsearchParseException("expected either field name [commands]; or start array; got [{}] instead"; token);
 }
 while ((token = parser.nextToken()) != XContentParser.Token.END_ARRAY) {
 if (token == XContentParser.Token.START_OBJECT) {
 // move to the command name
 token = parser.nextToken();

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content