Log ScriptService close failed – How To Solve Related Issues

Log ScriptService close failed – How To Solve Related Issues

Updated: Feb-20

Elasticsearch Version: 1.7-8.0

Background

To resolve issues causing many log errors you can try our Elasticsearch Check-Up it analyses ES configuration to provide actionable recommendations (no installation required) 


To troubleshoot log “ScriptService close failed” it’s important to understand a few problems related to Elasticsearch concepts node. See bellow important tips and explanations on these concepts

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();




Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Scripts Of Type Inline Operation Ag  

Errors After Updating To 6 2 4  

 

About Opster

Opster detects, resolves, optimizes, automates and prevents incidents in Elasticsearch. Opster’s line of products delivers a fundamentally more effective Elasticsearch operation and backs it up with superb production support and consulting.

Find Configuration Errors

Analyze Now