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

Opster Team

Aug-23, Version: 1.3-1.3

Briefly, this error occurs when Elasticsearch is unable to delete an index during the shutdown process. This could be due to insufficient permissions, a locked index, or a network issue. To resolve this, you can manually delete the index using the DELETE API, ensure that Elasticsearch has the necessary permissions, unlock the index if it’s locked, or check your network connection. If the issue persists, consider checking the Elasticsearch logs for more detailed error information.

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
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                public void run() {
                    try {
                        removeIndex(index; "shutdown"; shardsStopExecutor);
                    } catch (Throwable e) {
                        logger.warn("failed to delete index on stop [" + index + "]"; e);
                    } 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?