Briefly, this error occurs when Elasticsearch attempts to update the state of a task that doesn’t exist. This could be due to a task being deleted or completed before the update operation. To resolve this issue, you can ensure that tasks are not deleted or completed prematurely. Alternatively, you can implement error handling to catch this exception and handle it appropriately, such as by creating the task if it doesn’t exist or skipping the update operation if the task is not found.
This guide will help you check for common problems that cause the log ” trying to update state on non-existing task {} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: task, persistent.
Overview
A task is an Elasticsearch operation, which can be any request performed on an Elasticsearch cluster, such as a delete by query request, a search request and so on. Elasticsearch provides a dedicated Task API for the task management which includes various actions, from retrieving the status of current running tasks to canceling any long running task.
Examples
Get all currently running tasks on all nodes of the cluster
Apart from other information, the response of the below request contains task IDs of all the tasks which can be used to get detailed information about the particular task in question.
GET _tasks
Get detailed information of a particular task
Where clQFAL_VRrmnlRyPsu_p8A:1132678759 is the ID of the task in below request
GET _tasks/clQFAL_VRrmnlRyPsu_p8A:1132678759
Get all the current tasks running on particular nodes
GET _tasks?nodes=nodeId1,nodeId2
Cancel a task
Where clQFAL_VRrmnlRyPsu_p8A:1132678759 is the ID of the task in the below request
POST /_tasks/clQFAL_VRrmnlRyPsu_p8A:1132678759/_cancel?pretty
Notes
- The Task API will be most useful when you want to investigate the spike of resource utilization in the cluster or want to cancel an operation.
Overview
In Elasticsearch, persistent refers to cluster settings that persist across cluster restarts. This setting is used in Cluster Update API calls. Persistent settings can also be configured in the elasticsearch.yml file.
Examples
## enable shard routing
PUT /_cluster/settings
{
"persistent" : {
"cluster.routing.allocation.enable" : "all"
}
}
## enable rebalancing of shards
PUT /_cluster/settings
{
"persistent" : {
"cluster.routing.rebalance.enable" : "all"
}
}
## limit the heap size for fielddata
PUT /_cluster/settings
{
"persistent" : {
“indices.breaker.fielddata.limit”: "30%"
}
}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);
}
}
[ratemypost]
