Could not remove routing entries for removed or shutting down nodes – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.4-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch tries to remove routing entries for nodes that are either removed or shutting down, but fails to do so. This could be due to network issues, node failures, or incorrect configuration. To resolve this issue, you can try restarting the Elasticsearch cluster, ensuring that the nodes are correctly configured, or checking the network connectivity between the nodes. If the problem persists, you may need to manually remove the routing entries or consider upgrading your Elasticsearch version if it’s outdated.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” could not remove routing entries for removed or shutting down nodes ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, routing.

Log Context

Log “could not remove routing entries for removed or shutting down nodes” classname is TrainedModelAssignmentClusterService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                    return removeRoutingToUnassignableNodes(currentState);
                }

                @Override
                public void onFailure(Exception e) {
                    logger.error("could not remove routing entries for removed or shutting down nodes"; e);
                }

                @Override
                public void clusterStateProcessed(ClusterState oldState; ClusterState newState) {
                    logger.debug(

 

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?