Can t close autodetect – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.6-7.6

Briefly, this error occurs when Elasticsearch machine learning feature tries to close a job but fails due to an issue with the autodetect process. This could be due to a lack of system resources or a problem with the job configuration. To resolve this issue, you can try to increase system resources, check the job configuration for errors, or restart the Elasticsearch node. If the problem persists, you may need to investigate further into the logs for more detailed error messages.

This guide will help you check for common problems that cause the log ” Can’t close autodetect ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Can’t close autodetect” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             // If submitting the operation to read the results from the process fails we need to close
            // the process too; so that other submitted operations to threadpool are stopped.
            try {
            } catch (IOException ioe) {
                logger.error("Can't close autodetect"; ioe);
            throw e;
        return new AutodetectCommunicator(job; environment; process; new StateStreamer(client); dataCountsReporter; processor; handler;
                xContentRegistry; autodetectWorkerExecutor);


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?