Still had forecasts executing Attempting to set them to failed – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.7-8.9

Briefly, this error occurs when Elasticsearch tries to shut down while machine learning jobs are still forecasting. This could be due to a large number of jobs, long running jobs, or insufficient resources. To resolve this, you can manually stop the jobs before shutting down, increase the system resources, or adjust the job parameters to reduce the execution time. Also, ensure that the system is properly monitored to avoid overloading.

This guide will help you check for common problems that cause the log ” [{}] still had forecasts {} executing. Attempting to set them to failed. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “[{}] still had forecasts {} executing. Attempting to set them to failed.” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


    void handleOpenForecasts() {
        try {
            if (runningForecasts.isEmpty() == false) {
                logger.warn("[{}] still had forecasts {} executing. Attempting to set them to failed."; jobId; runningForecasts.keySet());
                // There may be many docs in the results persistence queue. But we only want to bother updating the running forecasts
                for (ForecastRequestStats forecastRequestStats : runningForecasts.values()) {
                    ForecastRequestStats failedStats = new ForecastRequestStats(forecastRequestStats);


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?