Failed to delete river on stop – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 1.7-1.7

Briefly, this error occurs when Elasticsearch tries to delete a river (a data feed mechanism) during the stop process, but fails. This could be due to the river not existing, insufficient permissions, or a network issue. To resolve this, ensure the river exists before deletion, check the user has the correct permissions to delete rivers, and verify the network connection is stable. If the river is no longer needed, you can ignore this error. However, if it’s required, recreate it and ensure it’s functioning properly.

This guide will help you check for common problems that cause the log ” failed to delete river on stop [{}]/[{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: delete.

Log Context

Log “failed to delete river on stop [{}]/[{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                public void run() {
                    try {
                    } catch (Exception e) {
                        logger.warn("failed to delete river on stop [{}]/[{}]"; e; riverName.type();;
                    } finally {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?