failed to delete index – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” failed to delete index ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: delete, index and indices.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

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

             success = true;
        } catch (ShardLockObtainFailedException ex) {
            logger.debug(() -> new ParameterizedMessage("{} failed to delete index store - at least one shards is still locked"; index);
                ex);
        } catch (Exception ex) {
            logger.warn(() -> new ParameterizedMessage("{} failed to delete index"; index); ex);
        } finally {
            if (success == false) {
                addPendingDelete(index; indexSettings);
            }
            // this is a pure protection to make sure this index doesn't get re-imported as a dangling index.




 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content