Successfully completed ML maintenance task triggerDeleteJobsInStateDeletingWithoutDeletionTask – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.8-8.9

Briefly, this error occurs when Elasticsearch Machine Learning (ML) jobs are in a deleting state but no deletion task is running. This is a maintenance task that Elasticsearch performs to clean up ML jobs that are marked for deletion but haven’t been deleted yet. To resolve this issue, you can manually delete the ML jobs using the Delete Job API. Alternatively, you can restart the Elasticsearch node to refresh the system and potentially clear the deleting state of the jobs. Lastly, ensure that there are no issues with your cluster’s health that could be causing delays in task processing.

This guide will help you check for common problems that cause the log ” Successfully completed [ML] maintenance task: triggerDeleteJobsInStateDeletingWithoutDeletionTask ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, task, delete.

Log Context

Log “Successfully completed [ML] maintenance task: triggerDeleteJobsInStateDeletingWithoutDeletionTask” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                    .filter(t -> t.v2().isAcknowledged() == false)
                if (jobIds.isEmpty()) {
          "Successfully completed [ML] maintenance task: triggerDeleteJobsInStateDeletingWithoutDeletionTask");
                } else {
          "The following ML jobs could not be deleted: [" + String.join(";"; jobIds) + "]");


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?