Completed deletion of expired ML data – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many 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.

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: delete and plugin.

Log Context

Log “Completed deletion of expired ML data” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             // thread is a disaster.
            remover.remove(new ThreadedActionListener(logger; threadPool; executor; nextListener; false);
        } else {
            if (haveAllPreviousDeletionsCompleted) {
      "Completed deletion of expired ML data");
            } else {
      "Halted deletion of expired ML data until next invocation");
            listener.onResponse(new DeleteExpiredDataAction.Response(haveAllPreviousDeletionsCompleted));


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content