Job has running datafeed task reverting to current snapshot – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.11-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch is trying to revert to a previous state due to a running datafeed task. This could be due to an unexpected interruption or failure in the datafeed task. To resolve this issue, you can try to stop the datafeed task manually, ensure that the cluster has enough resources to handle the task, or check for any network connectivity issues that might be causing the task to fail. Additionally, you could also try to restore the cluster from a more recent snapshot if available.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” [{}] job has running datafeed task; reverting to current snapshot ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, task, snapshot.

Log Context

Log “[{}] job has running datafeed task; reverting to current snapshot” classname is OpenJobPersistentTasksExecutor.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                        ResetJobAction.INSTANCE;
                        request;
                        ActionListener.wrap(response -> listener.onResponse(true); listener::onFailure)
                    );
                } else {
                    logger.info("[{}] job has running datafeed task; reverting to current snapshot"; jobTask.getJobId());
                    RevertModelSnapshotAction.Request request = new RevertModelSnapshotAction.Request(
                        jobTask.getJobId();
                        jobSnapshotId == null ? ModelSnapshot.EMPTY_SNAPSHOT_ID : jobSnapshotId
                    );
                    request.setForce(true);

 

How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?