Trying to update state on non-existing task – How to solve related issues

Trying to update state on non-existing task – 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 ” Trying to update state on non-existing task ” 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 “Trying to update state on non-existing task {}” classname is PersistentTasksClusterService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     return update(currentState; tasksInProgress.updateTaskState(taskId; taskState));
                } else {
                    if (tasksInProgress.hasTask(taskId)) {
                        logger.warn("trying to update state on task {} with unexpected allocation id {}"; taskId; taskAllocationId);
                    } else {
                        logger.warn("trying to update state on non-existing task {}"; taskId);
                    }
                    throw new ResourceNotFoundException("the task with id {} and allocation id {} doesn't exist"; taskId; taskAllocationId);
                }
            }





 

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

Analyze your cluster