Log Cant close autodetect – How To Solve Related Issues


Log Cant close autodetect – How To Solve Related Issues

Opster Team

Jan-20, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Cant close autodetect ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log “Can’t close autodetect” classname is AutodetectProcessManager.java
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 {
                IOUtils.close(process);
            } 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);




 

Optimize Elasticsearch Performance

Try The Tool