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.
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 TransportRevertModelSnapshotAction.java.
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();
logger.info("[{}] 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);
}
