Briefly, this error occurs when Elasticsearch encounters multiple models for a single job ID. This could be due to a duplication issue or a synchronization problem. To resolve this, you can try the following: 1) Check for any duplicate job IDs and remove them. 2) Ensure that the job ID is unique for each job. 3) If the issue persists, consider reindexing your data. 4) Lastly, check your cluster health and ensure all nodes are properly synchronized.
This guide will help you check for common problems that cause the log ” More than one model found for [job_id: ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “More than one model found for [job_id: ” classname is TransportDeleteModelSnapshotAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
jobResultsProvider.modelSnapshots(
request.getJobId(); 0; 1; null; null; null; true; request.getSnapshotId();
page -> {
List deleteCandidates = page.results();
if (deleteCandidates.size() > 1) {
logger.warn("More than one model found for [job_id: " + request.getJobId()
+ "; snapshot_id: " + request.getSnapshotId() + "] tuple.");
}
if (deleteCandidates.isEmpty()) {
listener.onFailure(new ResourceNotFoundException(Messages.getMessage(Messages.REST_NO_SUCH_MODEL_SNAPSHOT;
