Log Failed to delete river on stop – How To Solve Related Issues

Log Failed to delete river on stop – 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 “Failed to delete river on stop” it’s important to understand a few problems related to Elasticsearch concepts delete. See bellow important tips and explanations on these concepts

Log Context

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

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



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 :

1 Stopping Elasticsearch Failed To De  

Github Issue Number 2587  

 

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