Halted deletion of expired ML data until next invocation – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch’s Machine Learning (ML) feature tries to delete expired data but encounters an issue, causing the deletion process to stop until the next scheduled deletion. This could be due to insufficient permissions, a full disk, or a network issue. To resolve this, ensure that the Elasticsearch process has the necessary permissions to delete data. Also, check the disk space and free up some if it’s full. Lastly, verify your network connectivity and settings. Restarting the Elasticsearch service may also help.

This guide will help you check for common problems that cause the log ” Halted deletion of expired ML data until next invocation ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Halted deletion of expired ML data until next invocation” classname is TransportDeleteExpiredDataAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                        for (String jobId : request.getExpandedJobIds()) {
                            auditor.warning(jobId; msg);
                } else {
                    logger.info("Halted deletion of expired ML data until next invocation");
            listener.onResponse(new DeleteExpiredDataAction.Response(haveAllPreviousDeletionsCompleted));


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?