Briefly, this error occurs when Elasticsearch tries to reset a job that has a running datafeed but no snapshot exists. This could be due to a system crash or an abrupt shutdown. To resolve this issue, you can try the following: 1) Stop the datafeed task and then try resetting the job. 2) If the problem persists, you may need to create a new snapshot. 3) If none of these work, consider restarting the Elasticsearch cluster, but be aware that this should be a last resort as it can impact all running tasks.
This guide will help you check for common problems that cause the log ” [{}] job has running datafeed task; resetting as no snapshot exists ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, task, snapshot.
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.
Log Context
Log “[{}] job has running datafeed task; resetting as no snapshot exists” classname is OpenJobPersistentTasksExecutor.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
// We requested a single concrete job so if it didn't exist we would get an error
assert jobPage.size() == 1;
String jobSnapshotId = jobPage.get(0).getModelSnapshotId();
if (jobSnapshotId == null && isMasterNodeVersionOnOrAfter(ResetJobAction.VERSION_INTRODUCED)) {
logger.info("[{}] job has running datafeed task; resetting as no snapshot exists"; jobTask.getJobId());
ResetJobAction.Request request = new ResetJobAction.Request(jobTask.getJobId());
request.setSkipJobStateValidation(true);
request.masterNodeTimeout(PERSISTENT_TASK_MASTER_NODE_TIMEOUT);
request.timeout(PERSISTENT_TASK_MASTER_NODE_TIMEOUT);
executeAsyncWithOrigin(
