Briefly, this error occurs when Elasticsearch fails to delete its internal indices, which are used for management purposes. This could be due to insufficient permissions, a locked index, or a network issue. To resolve this, you can try the following: 1) Ensure the user has the necessary permissions to delete indices. 2) Check if the index is locked and unlock it if necessary. 3) Investigate for any network issues that might be preventing the operation. 4) If the issue persists, consider restarting the Elasticsearch cluster, but be aware of potential data loss.
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: plugin, indices, delete.
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” class name 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));
}
