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

Opster Team

August-23, Version: 8-8.2

Briefly, this error occurs when Elasticsearch tries to allocate a machine learning model to a node, but the model is not routed to the specified node. This could be due to a misconfiguration or a network issue. To resolve this, you can try reconfiguring the routing settings, checking the network connectivity between nodes, or reallocating the model to a different node. Additionally, ensure that the node has sufficient resources to handle the model.

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

Log Context

Log “allocation 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 :

 return currentState;
 if (existingAllocation.isRoutedToNode(nodeId) == false) {
 throw new ResourceNotFoundException("allocation for model with id [{}]] is not routed to node [{}]"; modelId; nodeId);
 builder.getAllocation(modelId).updateExistingRoutingEntry(nodeId; request.getRoutingState()).calculateAndSetAllocationState();  return update(currentState; builder);


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?