Failed to delete index on stop – 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.

Briefly, this error message usually indicates that Elasticsearch was unable to delete an index because it was in the process of shutting down. To resolve this issue, you can try restarting Elasticsearch and then attempting to delete the index again.

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 ” Failed to delete index on stop ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: delete, index and indices.

Log Context

Log “failed to delete index on stop [” classname is InternalIndicesService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 
Override
                public void run() {
                    try {
                        removeIndex(index; "shutdown"; shardsStopExecutor);
                    } catch (Throwable e) {
                        logger.warn("failed to delete index on stop [" + index + "]"; e);
                    } finally {
                        latch.countDown();
                    }
                }
            });



 

Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content