ScriptService close failed – How to solve related issues

Average Read Time

2 Mins

ScriptService close failed – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run 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 ” ScriptService close failed ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: node.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “ScriptService close failed” classname is Node.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 
        stopWatch.stop().start("script");
        try {
            injector.getInstance(ScriptService.class).close();
        } catch (IOException e) {
            logger.warn("ScriptService close failed"; e);
        }

        stopWatch.stop().start("thread_pool");
        // TODO this should really use ThreadPool.terminate()
        injector.getInstance(ThreadPool.class).shutdown();




 

Run the free Check-Up to get customized insights on your system:

Analyze your cluster

Skip to content