JobId failed to get job during ML memory update – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.2

Briefly, this error occurs when Elasticsearch Machine Learning (ML) fails to retrieve a job during a memory update. This could be due to issues like insufficient memory, incorrect job ID, or network connectivity problems. To resolve this, you can try increasing the memory allocation for Elasticsearch, ensure the job ID is correct, or check your network connection. Additionally, check the Elasticsearch logs for more detailed error information.

This guide will help you check for common problems that cause the log ” [” + jobId + “] failed to get job during ML memory update ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, memory.

Log Context

Log “[” + jobId + “] failed to get job during ML memory update” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        }; e -> {
            if (e instanceof ResourceNotFoundException) {
                // TODO: does this also happen if the .ml-config index exists but is unavailable?
                logger.trace("[{}] job deleted during ML memory update"; jobId);
            } else {
                logger.error("[" + jobId + "] failed to get job during ML memory update"; e);


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?