Briefly, this error occurs when Elasticsearch attempts to add a method to its blacklist, which is a list of methods that are prohibited from being used due to potential security risks or performance issues. This could be due to a deprecated method or a method that is causing issues in the system. To resolve this issue, you can either stop using the blacklisted method in your queries or replace it with a safer or more efficient alternative. Additionally, ensure your Elasticsearch version is up-to-date as some methods may be blacklisted in older versions but allowed in newer ones.
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.
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();
