Briefly, this error occurs when you attempt to delete system indices directly in Elasticsearch. System indices are crucial for Elasticsearch’s internal operations and deleting them can disrupt its functionality. To resolve this issue, you can either avoid deleting system indices or use the “allow_no_indices” option to ignore the error if the index doesn’t exist. Additionally, ensure you have the correct permissions to perform such operations. Lastly, always backup your data before making any major changes to prevent data loss.
This guide will help you check for common problems that cause the log ” [{}] deleting the following indices directly {} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: indices, plugin.
Log Context
Log “[{}] deleting the following indices directly {}” classname is JobDataDeleter.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
final boolean needToRunDBQ = needToRunDBQTemp;
if (indicesToDelete.isEmpty()) {
deleteByQueryExecutor.onResponse(needToRunDBQ);
return;
}
logger.info("[{}] deleting the following indices directly {}"; jobId; indicesToDelete);
DeleteIndexRequest request = new DeleteIndexRequest(indicesToDelete.toArray(String[]::new));
request.indicesOptions(IndicesOptions.lenientExpandOpenHidden());
executeAsyncWithOrigin(
client.threadPool().getThreadContext();
ML_ORIGIN;
