The task wasnt found; status is not updated – How to solve related issues

The task wasnt found; status is not updated – 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 can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” The task wasnt found; status is not updated ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: cluster, persistent and task.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log “The task [{}] wasn’t found; status is not updated” classname is PersistentTasksClusterService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 } else {
                    if (tasksInProgress.hasTask(id)) {
                        logger.warn("The task [{}] with id [{}] was found but it has a different allocation id [{}]; status is not updated";
                                PersistentTasksCustomMetaData.getTaskWithId(currentState; id).getTaskName(); id; allocationId);
                    } else {
                        logger.warn("The task [{}] wasn't found; status is not updated"; id);
                    }
                    throw new ResourceNotFoundException("the task with id [" + id + "] and allocation id [" + allocationId + "] not found");
                }
            }





 

Run the Check-Up to get a customized report like this:

Analyze your cluster