Failed to get job configs to include in ML usage – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.17-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 unable to retrieve the configurations for Machine Learning (ML) jobs. This could be due to issues with the ML module, incorrect permissions, or network connectivity problems. To resolve this, you can check if the ML module is properly installed and enabled. Also, ensure that the user has the necessary permissions to access the ML jobs. Lastly, verify your network connections and settings. If the issue persists, consider checking the Elasticsearch logs for more detailed error information.

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 ” Failed to get job configs to include in ML usage ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Failed to get job configs to include in ML usage” classname is MachineLearningUsageTransportAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        ActionListener jobStatsListener = ActionListener.wrap(
            response -> jobManagerHolder.getJobManager().expandJobs(Metadata.ALL; true; ActionListener.wrap(jobs -> {
                addJobsUsage(response; jobs.results(); jobsUsage);
                client.execute(GetDatafeedsStatsAction.INSTANCE; datafeedStatsRequest; datafeedStatsListener);
            }; e -> {
                logger.warn("Failed to get job configs to include in ML usage"; e);
                client.execute(GetDatafeedsStatsAction.INSTANCE; datafeedStatsRequest; datafeedStatsListener);
            }));
            e -> {
                logger.warn("Failed to get job stats to include in ML usage"; e);
                client.execute(GetDatafeedsStatsAction.INSTANCE; datafeedStatsRequest; datafeedStatsListener);

 

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?