%s model routing info was updated with %s and master notified – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.4-8.7

Briefly, this error occurs when there is a change in the routing information of the Elasticsearch S model. This could be due to a change in the cluster state, such as adding or removing nodes, or updating the shard allocation. To resolve this issue, you can verify the cluster health and ensure all nodes are properly connected. If there are any disconnected nodes, reconnect them. Also, check the shard allocation and adjust it if necessary. Lastly, ensure that the master node is properly receiving and processing updates.

This guide will help you check for common problems that cause the log ” [%s] model routing info was updated with [%s] and master notified ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, routing, master.

Log Context

Log “[%s] model routing info was updated with [%s] and master notified” classname is TrainedModelAssignmentNodeService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            new UpdateTrainedModelAssignmentRoutingInfoAction.Request(nodeId; modelId; update);
            ActionListener.wrap(success -> {
                logger.debug(() -> format("[%s] model routing info was updated with [%s] and master notified"; modelId; update));
            }; error -> {
                logger.warn(() -> format("[%s] failed to update model routing info with [%s]"; modelId; update); error);


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?