Running DELETE Index on – How to solve related issues

Running DELETE Index on – 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 ” Running DELETE Index on ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: delete, index and plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log “Running DELETE Index on [” classname is TransportDeleteJobAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         ActionListener customIndexSearchHandler = ActionListener.wrap(
                searchResponse -> {
                    if (searchResponse == null || searchResponse.getHits().totalHits > 0) {
                        deleteByQueryExecutor.onResponse(true); // We need to run DBQ and alias deletion
                    } else {
                        logger.info("Running DELETE Index on [" + String.join("; "; indexNames.get()) + "] for job [" + jobId + "]");
                        DeleteIndexRequest request = new DeleteIndexRequest(indexNames.get());
                        request.indicesOptions(IndicesOptions.lenientExpandOpen());
                        // If we have deleted the index; then we don't need to delete the aliases or run the DBQ
                        executeAsyncWithOrigin(
                                parentTaskClient.threadPool().getThreadContext();




 

Run the Check-Up to get a customized report like this:

Analyze your cluster