Creating new model alias for model – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.13-8.9

Briefly, this error occurs when Elasticsearch tries to create a new alias for a model, but it encounters an issue. This could be due to a conflict with an existing alias, insufficient permissions, or a network issue. To resolve this, you can check if the alias already exists and delete it if necessary, ensure the user has the correct permissions to create an alias, or troubleshoot network connectivity. Additionally, check your Elasticsearch version and upgrade if necessary, as some versions may have bugs related to alias creation.

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

Log Context

Log “creating new model_alias [{}] for model [{}]” classname is TransportPutTrainedModelAliasAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        final ClusterState.Builder builder = ClusterState.builder(currentState);
        final ModelAliasMetadata currentMetadata = ModelAliasMetadata.fromState(currentState);
        String currentModelId = currentMetadata.getModelId(request.getModelAlias());
        final Map newMetadata = new HashMap(currentMetadata.modelAliases());
        if (currentModelId == null) {
            logger.info("creating new model_alias [{}] for model [{}]"; request.getModelAlias(); request.getModelId());
        } else {
            logger.info(
                "updating model_alias [{}] to refer to model [{}] from model [{}]";
                request.getModelAlias();
                request.getModelId();

 

 [ratemypost]