No river _meta document found after attempts – 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 ” No river _meta document found after attempts ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: document and routing.

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 “no river _meta document found after {} attempts” classname is RiversRouter.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 
        // At least one type does not have _meta; so we are
        // going to reschedule some checks
        if (!metaFound) {
            if (countDown.countDown()) {
                logger.warn("no river _meta document found after {} attempts"; RIVER_START_MAX_RETRIES);
            } else {
                logger.debug("no river _meta document found retrying in {} ms"; RIVER_START_RETRY_INTERVAL.millis());
                try {
                    threadPool.schedule(RIVER_START_RETRY_INTERVAL; ThreadPool.Names.GENERIC; new Runnable() {
                        
Override



 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content