Briefly, this error occurs when there is a change in the routing information of an Elasticsearch deployment. This could be due to adding or removing nodes, changing the network configuration, or adjusting shard allocation. To resolve this issue, you can verify the changes made to the routing information and ensure they are correct. If the changes were unintentional, revert them back. If the changes were intentional, ensure that all nodes are properly communicating with the master node. Also, check the health of your cluster to ensure it’s green and all shards are properly allocated.
This guide will help you check for common problems that cause the log ” [%s] deployment 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, master, routing.
Overview
In Elasticsearch, routing refers to document routing. When you index a document, Elasticsearch will determine which shard the document should be routed to for indexing.
The shard is selected based on the following formula:
shard = hash(_routing) % number_of_primary_shards
Where the default value of _routing is _id.
It is important to know which shard the document is routed to, because Elasticsearch will need to determine where to find that document later on for document retrieval requests.
Examples
In twitter index with 2 primary shards, the document with _id equal to “440” gets routed to the shard number:
shard = hash( 440 ) % 2
PUT twitter/_doc/440
{
...
}Notes and good things to know
- In order to improve search speed, you can create custom routing. For example, you can enable custom routing that will ensure that only a single shard will be queried (the shard that contains your data).
- To create custom routing in Elasticsearch, you will need to configure and define that not all routing will be completed by default settings. ( v <= 5.0)
PUT my_index/customer/_mapping
{
"order":{
"_routing":{
"required":true
}
}
}- This will ensure that every document in the “customer” type must specify a custom routing. For Elasticsearch version 6 or above you will need to update the same mapping as:
PUT my_index/_mapping
{
"order":{
"_routing":{
"required":true
}
}
}Log Context
Log “[%s] deployment 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 :
return;
}
trainedModelAssignmentService.updateModelAssignmentState(
new UpdateTrainedModelAssignmentRoutingInfoAction.Request(nodeId; deploymentId; update);
ActionListener.wrap(success -> {
logger.debug(() -> format("[%s] deployment routing info was updated with [%s] and master notified"; deploymentId; update));
listener.onResponse(AcknowledgedResponse.TRUE);
}; error -> {
logger.warn(() -> format("[%s] failed to update deployment routing info with [%s]"; deploymentId; update); error);
listener.onFailure(error);
})
