Starting to execute task – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.11-8.9

Briefly, this error occurs when Elasticsearch begins to execute a task. It’s not necessarily an error, but more of an informational message indicating that a task (like indexing, searching, or any other operation) has started. If you’re experiencing issues, they might be related to the specific task being executed. To resolve this, you could check the task’s parameters, ensure your cluster has sufficient resources, or look for any subsequent error messages that might indicate what went wrong with the task.

This guide will help you check for common problems that cause the log ” [{}] [{}] starting to execute task ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, task, snapshot.

Log Context

Log “[{}] [{}] starting to execute task” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

    protected void nodeOperation(AllocatedPersistentTask task; SnapshotUpgradeTaskParams params; PersistentTaskState state) {
        SnapshotUpgradeTaskState jobTaskState = (SnapshotUpgradeTaskState) state;
        SnapshotUpgradeState jobState = jobTaskState == null ? null : jobTaskState.getState();"[{}] [{}] starting to execute task"; params.getJobId(); params.getSnapshotId());

        // This means that we have loaded the snapshot and possibly snapshot was partially updated
        // This is no good; we should remove the snapshot
        if (SnapshotUpgradeState.SAVING_NEW_STATE.equals(jobState)) {
            deleteSnapshotAndFailTask(task; params.getJobId(); params.getSnapshotId());