More than one model found for jobid: – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” More than one model found for jobid: ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: delete, plugin and snapshot.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

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;




 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content