Opster Team
Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.
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 internal indices ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: delete, indices, plugin.
Overview
DELETE is an Elasticsearch API which removes a document from a specific index. This API requires an index name and _id document to delete the document.
Delete a document
DELETE /my_index/_doc/1
Notes
- A delete request throws 404 error code if the document does not already exist in the index.
- If you want to delete a set of documents that matches a query, you need to use delete by query API.
Log Context
Log “Failed to delete internal indices”classname is IndexBasedTransformConfigManager.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :
IndicesOptions.LENIENT_EXPAND_OPEN ); executeAsyncWithOrigin(client; TRANSFORM_ORIGIN; DeleteIndexAction.INSTANCE; deleteRequest; ActionListener.wrap(response -> { if (response.isAcknowledged() == false) { listener.onFailure(new ElasticsearchStatusException("Failed to delete internal indices"; RestStatus.INTERNAL_SERVER_ERROR)); return; } listener.onResponse(true); }; listener::onFailure)); }
Find & fix Elasticsearch problems
Opster AutoOps diagnoses & fixes issues in Elasticsearch based on analyzing hundreds of metrics.
Fix Your Cluster IssuesConnect in under 2 minutes
Billy McCarthy
Senior SysAdmin at Backblaze