Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues causing many log errors (free and no installation required)
This guide will help you check for common problems that cause the log “No river type provided for . ignoring” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: routing.
Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations.
Routing in Elasticsearch
What it is
In Elasticsearch, routing refers to document routing. When you index a document, Elasticsearch will determine which shard will be used to index the document to.
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
- In order to improve search performance speed you can create custom routing. For example, you can enable custom routing that will ensure only a single shard is 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 6 or above you will need to update the same mapping as:
PUT my_index/_mapping
{
"order":{
"_routing":{
"required":true
}
}
}
Log Context
Log”no river type provided for [{}]; ignoring…” classname is RiversRouter.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
logger.debug("{}/{}/_meta document found."; riverIndexName; mappingType);
String riverType = XContentMapValues.nodeStringValue(getResponse.getSourceAsMap().get("type"); null);
if (riverType == null) {
logger.warn("no river type provided for [{}]; ignoring..."; riverIndexName);
} else {
routingBuilder.put(new RiverRouting(new RiverName(riverType; mappingType); null));
dirty = true;
}
} else {
Related issues to this log
We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :
About Opster
Opster line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.
