Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration 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 ” Close job interrupted by kill request ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: request, plugin.
Log Context
Log “Close job interrupted by kill request”classname is AutodetectCommunicator.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :
} catch (InterruptedException e) {
Thread.currentThread().interrupt();
} catch (ExecutionException e) {
if (processKilled) {
// In this case the original exception is spurious and highly misleading
throw ExceptionsHelper.conflictStatusException("Close job interrupted by kill request");
} else {
throw FutureUtils.rethrowExecutionException(e);
}
} finally {
destroyCategorizationAnalyzer();
Find & fix Elasticsearch problems
