Delayed reroute ” + reason + ” could not be submitted – How to solve this Elasticsearch error

Opster Team

March-22, 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 ” delayed reroute ” + reason + ” could not be submitted ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster, routing.

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 “delayed reroute [” + reason + “] could not be submitted”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 ClusterState state = clusterService.state();
 logger.warn(() -> new ParameterizedMessage("failed to reroute routing table; current state:\n{}"; state); e);
 new ElasticsearchException("delayed reroute [" + reason + "] could not be submitted"; e)


Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content