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

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 Error 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. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the 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 which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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;
  }

Run the Check-Up to get a customized report like this:

check-up-dashboard illustration

Try The Tool