Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.
To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them. Take a self-guided product tour to see for yourself (no registration required).
This guide will help you check for common problems that cause the log ” Compiling script file ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery-file.
Log Context
Log “compiling script file [{}]” classname is ScriptService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
} else {
try {
//we don't know yet what the script will be used for; but if all of the operations for this lang
// with file scripts are disabled; it makes no sense to even compile it and cache it.
if (isAnyScriptContextEnabled(engineService.types()[0]; engineService; ScriptType.FILE)) {
logger.info("compiling script file [{}]"; file.toAbsolutePath());
try(InputStreamReader reader = new InputStreamReader(Files.newInputStream(file); Charsets.UTF_8)) {
String script = Streams.copyToString(reader);
CacheKey cacheKey = new CacheKey(engineService; scriptNameExt.v1(); null; Collections.emptyMap());
staticCache.put(cacheKey; new CompiledScript(ScriptType.FILE; scriptNameExt.v1(); engineService.types()[0]; engineService.compile(script; Collections.emptyMap())));
scriptMetrics.onCompilation();
