Cannot delete model as it is still referenced by ingest processors – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

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

This guide will help you check for common problems that cause the log ” Cannot delete model as it is still referenced by ingest processors ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: delete and plugin.

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 “Cannot delete model [{}] as it is still referenced by ingest processors”classname  is TransportDeleteTrainedModelAction.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

String id = request.getId();
 IngestMetadata currentIngestMetadata = state.metadata().custom(IngestMetadata.TYPE);
 Set referencedModels = getReferencedModelKeys(currentIngestMetadata); 
 if (referencedModels.contains(id)) {
 listener.onFailure(new ElasticsearchStatusException("Cannot delete model [{}] as it is still referenced by ingest processors";
 RestStatus.CONFLICT;
 id));
 return;
 }

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content