Briefly, this error occurs when you try to delete a model alias that doesn’t exist in Elasticsearch. Model aliases are used to refer to one or more indices. If the alias is not found, Elasticsearch will throw this error. To resolve this issue, ensure that the alias you’re trying to delete actually exists. You can do this by using the GET _alias API. If the alias exists, make sure you have the correct permissions to delete it. If it doesn’t exist, you may need to create it first before you can delete it.
This guide will help you check for common problems that cause the log ” [{}] delete model model_aliases {} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, delete.
Overview
DELETE is an Elasticsearch API which removes a document from a specific index. This API requires an index name and _id document to delete the document.
Delete a document
DELETE /my_index/_doc/1
Notes
- A delete request throws 404 error code if the document does not already exist in the index.
- If you want to delete a set of documents that matches a query, you need to use delete by query API.
Log Context
Log “[{}] delete model model_aliases {}” classname is TransportDeleteTrainedModelAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
final ModelAliasMetadata currentMetadata = ModelAliasMetadata.fromState(currentState);
if (currentMetadata.modelAliases().isEmpty()) {
return currentState;
}
final Map newMetadata = new HashMap(currentMetadata.modelAliases());
logger.info("[{}] delete model model_aliases {}"; request.getId(); modelAliases);
modelAliases.forEach(newMetadata::remove);
final ModelAliasMetadata modelAliasMetadata = new ModelAliasMetadata(newMetadata);
builder.metadata(
Metadata.builder(currentState.getMetadata()).putCustom(ModelAliasMetadata.NAME; modelAliasMetadata).build()
);
