Model alias could not be found – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.13-8.9

Briefly, this error occurs when Elasticsearch tries to access a model alias that doesn’t exist in the system. This could be due to a typo in the alias name, or the alias was not properly created. To resolve this issue, you can verify the alias name for any typos or check if the alias was correctly created. If the alias doesn’t exist, you need to create it. If it’s a typo, correct it in your query. Also, ensure that the alias is associated with the correct index.

This guide will help you check for common problems that cause the log ” model_alias [{}] could not be found ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “model_alias [{}] could not be found” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 final DeleteTrainedModelAliasAction.Request request
 ) {
 final ModelAliasMetadata currentMetadata = ModelAliasMetadata.fromState(currentState);
 final String referencedModel = currentMetadata.getModelId(request.getModelAlias());
 if (referencedModel == null) {
 throw new ElasticsearchStatusException("model_alias [{}] could not be found"; RestStatus.NOT_FOUND; request.getModelAlias());
 if (referencedModel.equals(request.getModelId()) == false) {
 throw new ElasticsearchStatusException(
 "model_alias [{}] does not refer to provided model_id [{}]";