Removing intervening records after reverting model deleting results after – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.8-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 attempts to revert changes to a model and delete the results that were produced in the intervening period. This could be due to a conflict in the data or an issue with the model itself. To resolve this issue, you could try to identify and resolve the conflict in the data, or you could attempt to rebuild the model. Additionally, ensure that the Elasticsearch cluster is healthy and that there are no issues with the underlying hardware or network.

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 ” [{}] Removing intervening records after reverting model: deleting results after [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “[{}] Removing intervening records after reverting model: deleting results after [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        // If we need to delete buckets that occurred after the snapshot; we
        // wrap the listener with one that invokes the OldDataRemover on
        // acknowledged responses
        return ActionListener.wrap(response -> {
            Date deleteAfter = modelSnapshot.getLatestResultTimeStamp() == null ? new Date(0) : modelSnapshot.getLatestResultTimeStamp();
  "[{}] Removing intervening records after reverting model: deleting results after [{}]"; jobId; deleteAfter);

            JobDataDeleter dataDeleter = new JobDataDeleter(client; jobId);
            dataDeleter.deleteResultsFromTime(deleteAfter.getTime() + 1; listener.delegateFailure((l; r) -> l.onResponse(response)));
        }; listener::onFailure);


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?