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

Opster Team

Aug-23, Version: 7.17-8.9

Briefly, this error occurs when Elasticsearch is unable to retrieve statistics for Machine Learning (ML) jobs, which are crucial for monitoring and managing ML operations. This could be due to issues like insufficient permissions, network problems, or a malfunctioning ML module. To resolve this, ensure that the user has the necessary permissions to access ML job stats. Check the network connectivity between Elasticsearch nodes. Also, verify the health of the ML module and restart it if necessary. If the problem persists, consider checking the Elasticsearch logs for more detailed error information.

This guide will help you check for common problems that cause the log ” Failed to get job stats 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 stats to include in ML usage” classname is MachineLearningUsageTransportAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            }; 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);
            }
        );

        // Step 0. Kick off the chain of callbacks by requesting jobs stats

 

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?