Cancelling reset task because delete was requested – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.14-8.9

Briefly, this error occurs when an Elasticsearch reset task is cancelled due to a delete request. This typically happens when a delete operation is performed on an index while a reset task is ongoing. To resolve this issue, you can either wait for the reset task to complete before performing the delete operation or cancel the reset task manually before initiating the delete operation. Additionally, ensure that no automated scripts or applications are sending conflicting requests to Elasticsearch.

This guide will help you check for common problems that cause the log ” [{}] Cancelling reset task [{}] because delete was requested ” 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 “[{}] Cancelling reset task [{}] because delete was requested” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

    private void cancelResetTaskIfExists(String jobId; ActionListener listener) {
        ActionListener jobListener = ActionListener.wrap(jobBuilder -> {
            Job job =;
            if (job.getBlocked().getReason() == Blocked.Reason.RESET) {
      "[{}] Cancelling reset task [{}] because delete was requested"; jobId; job.getBlocked().getTaskId());
                CancelTasksRequest cancelTasksRequest = new CancelTasksRequest();
                cancelTasksRequest.setReason("deleting job");