Rivers have been deprecated. Read – 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 analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them. Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” Rivers have been deprecated. Read ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “rivers have been deprecated. Read https://www.elastic.co/blog/deprecating_rivers” classname is RiversService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         if (riversInjectors.containsKey(riverName)) {
            logger.warn("ignoring river [{}][{}] creation; already exists"; riverName.type(); riverName.name());

        logger.info("rivers have been deprecated. Read https://www.elastic.co/blog/deprecating_rivers");
        logger.debug("creating river [{}][{}]"; riverName.type(); riverName.name());

        try {
            ModulesBuilder modules = new ModulesBuilder();
            modules.add(new RiverNameModule(riverName));


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content