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

Opster Team

August-23, Version: 8.3-8.7

Briefly, this error occurs when Elasticsearch tries to assign a shard to a node, but the routing configuration doesn’t allow it. This could be due to incorrect shard allocation settings or a misconfigured cluster. To resolve this issue, you can check and correct your shard allocation settings, ensure that your cluster is properly configured, or manually reroute the shard using the reroute API. Also, make sure that the node has enough resources to handle the shard.

This guide will help you check for common problems that cause the log ” assignment for model 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: node, plugin.

Log Context

Log “assignment for model 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 :

 () -> format("[%s] requested update from node [%s] while stopping; update was [%s]"; modelId; nodeId; request.getUpdate())
 return currentState;
 if (existingAssignment.isRoutedToNode(nodeId) == false) {
 throw new ResourceNotFoundException("assignment for model with id [{}]] is not routed to node [{}]"; modelId; nodeId);
 RoutingInfo routingInfo = existingAssignment.getNodeRoutingTable().get(nodeId);
 .updateExistingRoutingEntry(nodeId; request.getUpdate().apply(routingInfo))