Failed to reroute routing table; current state:n – How to solve related issues

Average Read Time

2 Mins

Failed to reroute routing table; current state:n – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Failed to reroute routing table; current state:n ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster and 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 “Failed to reroute routing table; current state:n{}” classname is RoutingService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     }
                });
        } catch (Exception e) {
            rerouting.set(false);
            ClusterState state = clusterService.state();
            logger.warn(() -> new ParameterizedMessage("failed to reroute routing table; current state:\n{}"; state); e);
        }
    }
}






 

Run the Check-Up to get customized insights on your system:

Analyze your cluster