meta document not found – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” meta document not found ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: document.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “{}/{}/_meta document not found” classname is RiversService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                             if (getResponse.isExists()) {
                                // only create the river if it exists; otherwise; the indexing meta data has not been visible yet...
                                createRiver(routing.riverName(); getResponse.getSourceAsMap());
                            } else {
                                //this should never happen as we've just found the _meta document in RiversRouter
                                logger.warn("{}/{}/_meta document not found"; riverIndexName; routing.riverName().getName());
                            }
                        }
                    }

                    
Override



 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content