Created ML annotations index and aliases – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run 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 ” Created ML annotations index and aliases ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: aliases, index 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 “Created ML annotations index and aliases” classname is MlInitializationService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         if (event.localNodeMaster() && isIndexCreationInProgress.compareAndSet(false; true)) {
            AnnotationIndex.createAnnotationsIndexIfNecessary(settings; client; event.state(); ActionListener.wrap(
                r -> {
                    isIndexCreationInProgress.set(false);
                    if (r) {
                        logger.info("Created ML annotations index and aliases");
                    }
                };
                e -> {
                    isIndexCreationInProgress.set(false);
                    logger.error("Error creating ML annotations index or aliases"; e);




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content