Assignment with id is not routed to node – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 8.8-8.9

Briefly, this error occurs when Elasticsearch tries to assign a shard to a node, but the shard is not routed to that specific node. This could be due to a misconfiguration or a network issue. To resolve this, you can try to manually reroute the shard to the correct node using the Cluster Reroute API. Alternatively, check your cluster health and ensure all nodes are properly connected. If the issue persists, consider checking your shard allocation settings or restarting the Elasticsearch cluster.

This guide will help you check for common problems that cause the log ” assignment with id [{}]] is not routed to node [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, node.

Log Context

Log “assignment with id [{}]] is not routed to node [{}]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 return currentState;
 if (existingAssignment.isRoutedToNode(nodeId) == false) {
 throw new ResourceNotFoundException("assignment with id [{}]] is not routed to node [{}]"; deploymentId; nodeId);
 RoutingInfo routingInfo = existingAssignment.getNodeRoutingTable().get(nodeId);
 .updateExistingRoutingEntry(nodeId; request.getUpdate().apply(routingInfo))


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?