Briefly, this error occurs when the Elasticsearch Machine Learning (ML) feature automatically deletes expired data. This is a routine process and not an error. It’s part of the system’s self-maintenance to ensure optimal performance. However, if you believe data is being deleted prematurely, you can adjust the data retention settings in your Elasticsearch configuration. Alternatively, if you want to keep all data indefinitely, you can disable this automatic deletion feature, but be aware this could impact system performance.
This guide will help you check for common problems that cause the log ” Completed deletion of expired ML data ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “Completed deletion of expired ML data” classname is TransportDeleteExpiredDataAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
new ThreadedActionListener(threadPool.executor(executor); nextListener);
isTimedOutSupplier
);
} else {
if (haveAllPreviousDeletionsCompleted) {
logger.info("Completed deletion of expired ML data");
} else {
if (isTimedOutSupplier.getAsBoolean()) {
TimeValue timeoutPeriod = request.getTimeout() == null ? MlDataRemover.DEFAULT_MAX_DURATION : request.getTimeout();
String msg = "Deleting expired ML data was cancelled after the timeout period of ["
+ timeoutPeriod
[ratemypost]
