Before you begin reading this guide, we recommend you try running the 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 override task with id ” + taskId + ” ” 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: task and persistent.
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).
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 override task with id {” + taskId + “}”classname is PersistentTasksCustomMetadata.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :
Assignment assignment) {
changed = true;
PersistentTask> previousTask = tasks.put(taskId; new PersistentTask(taskId; taskName; params;
getNextAllocationId(); assignment));
if (previousTask != null) {
throw new ResourceAlreadyExistsException("Trying to override task with id {" + taskId + "}");
}
return this;
}
/**
