Log No river type provided for . ignoring – How To Solve Related Issues

Log No river type provided for . ignoring – How To Solve Related Issues

Updated: Feb-20

Elasticsearch Version: 1.7-8.0

Background

To resolve issues causing many log errors you can try our Elasticsearch Check-Up it analyses ES configuration to provide actionable recommendations (no installation required) 


To troubleshoot log “No river type provided for . ignoring” it’s important to understand a few problems related to Elasticsearch concepts routing. See bellow important tips and explanations on these concepts

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 detects, resolves, optimizes, automates and prevents incidents in Elasticsearch. Opster’s line of products delivers a fundamentally more effective Elasticsearch operation and backs it up with superb production support and consulting.

Find Configuration Errors

Analyze Now