No commands – 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 ” No commands ” 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 “No commands”classname  is AllocationCommands.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

public static AllocationCommands fromXContent(XContentParser parser) throws IOException {
 AllocationCommands commands = new AllocationCommands(); 
 XContentParser.Token token = parser.currentToken();
 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());
 }

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content