Delayed reroute reason could not be submitted – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.3-8.9

Briefly, this error occurs when Elasticsearch fails to submit a delayed reroute operation. This could be due to a variety of reasons such as network issues, node failures, or cluster health problems. To resolve this issue, you can try restarting the Elasticsearch service, checking the network connectivity, ensuring the cluster health is green, or increasing the cluster reroute timeout setting. If the problem persists, you may need to investigate the underlying cause in more detail, such as checking the Elasticsearch logs for more specific error messages.

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

Log Context

Log “delayed reroute [” + reason + “] could not be submitted” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 ClusterState state = clusterService.state();
 logger.warn(() -> "failed to reroute routing table; current state:\n" + state; e);
 new ElasticsearchException("delayed reroute [" + reason + "] could not be submitted"; e)
 }  @SuppressForbidden(reason = "legacy usage of unbatched task") // TODO add support for batching here


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?