Expected field name to be named commands got instead – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch expects a field named “commands” in the request body, but it receives an empty object or a different field name. This could be due to a typo or incorrect formatting in the request. To resolve this issue, you should check the request body and ensure that the field name is correctly spelled as “commands”. Also, make sure that the field is not empty and contains valid data. If the error persists, check the Elasticsearch version as the field name might have changed in different versions.

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, cluster.

Log Context

Log “expected field name to be named [commands]; got [{}] instead” class name 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") == false) {
 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");


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?