Starting machine learning feature reset – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.13-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch is trying to reset the machine learning features, possibly due to an issue with the machine learning jobs or datafeeds. This could be due to a configuration issue, a problem with the underlying data, or a bug in Elasticsearch itself. To resolve this issue, you could try stopping all machine learning jobs and datafeeds, checking the configuration settings, or upgrading Elasticsearch to the latest version. If the problem persists, you may need to delete and recreate the machine learning jobs or datafeeds.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” Starting machine learning feature reset ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Starting machine learning feature reset” classname is MachineLearning.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            // if ML is disabled; the custom cleanup can fail; but we can still clean up indices
            // by calling the superclass cleanup method
            SystemIndexPlugin.super.cleanUpFeature(clusterService; unwrappedClient; finalListener);
            return;
        }
        logger.info("Starting machine learning feature reset");
        OriginSettingClient client = new OriginSettingClient(unwrappedClient; ML_ORIGIN);

        final Map results = new ConcurrentHashMap();

        ActionListener unsetResetModeListener = ActionListener.wrap(

 

How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?