Adding to . new blacklisted methods – 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 ” Adding to . new blacklisted methods ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: thread.

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 “adding {} to [{}]; new blacklisted methods: {}” classname is ScriptService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             GroovyScriptEngineService engine = (GroovyScriptEngineService) ScriptService.this.scriptEnginesByLang.get(GroovyScriptEngineService.NAME);
            if (engine != null) {
                String[] patches = settings.getAsArray(GroovyScriptEngineService.GROOVY_SCRIPT_BLACKLIST_PATCH; Strings.EMPTY_ARRAY);
                boolean blacklistChanged = engine.addToBlacklist(patches);
                if (blacklistChanged) {
                    logger.info("adding {} to [{}]; new blacklisted methods: {}"; patches;
                            GroovyScriptEngineService.GROOVY_SCRIPT_BLACKLIST_PATCH; engine.blacklistAdditions());
                    engine.reloadConfig();
                    // Because the GroovyScriptEngineService knows nothing about the
                    // cache; we need to clear it here if the setting changes
                    ScriptService.this.clearCache();




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content