The task has been stopped while waiting to be started – How to solve this Elasticsearch error

Opster Team

March-22, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration 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 ” the task has been stopped while waiting to be started ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, task.

Log Context

Log “the task has been stopped while waiting to be started”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

switch (analyticsState) {
 case STARTED:
 node = persistentTask.getExecutorNode();
 return true;
 exception = ExceptionsHelper.conflictStatusException("the task has been stopped while waiting to be started");
 return true;
 // The STARTING case here is expected to be incredibly short-lived; just occurring during the
 // time period when a job has successfully been assigned to a node but the request to update
 // its task state is still in-flight. (The long-lived STARTING case when a lazy node needs to
 // be added to the cluster to accommodate the job was dealt with higher up this method when the


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content