Delayed reroute reason cancelled – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.3-8.2

Briefly, this error occurs when an Elasticsearch cluster tries to rebalance itself or recover from a node failure, but the process is interrupted or cancelled. This could be due to network issues, node failures, or configuration problems. To resolve this issue, you can check the cluster’s health and logs to identify any problematic nodes or network issues. You may also need to adjust the cluster settings or increase the timeout values to allow for longer reroute operations. Additionally, ensure that your Elasticsearch version is up-to-date to avoid any known bugs.

This guide will help you check for common problems that cause the log ” delayed reroute [” + reason + “] cancelled ” 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 + “] cancelled” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 synchronized (mutex) {
 if (pendingRerouteListeners == currentListeners) {
 pendingRerouteListeners = null;
 ActionListener.onFailure(currentListeners; new NotMasterException("delayed reroute [" + reason + "] cancelled"));
 // no big deal; the new master will reroute again
 }  @Override
 public void onFailure(Exception e) {


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?