Briefly, this error occurs when Elasticsearch is unable to retrieve the ID of a job that has been terminated, due to a timeout. This could be due to high load, slow network, or a large queue of pending tasks. To resolve this issue, you can increase the timeout setting, optimize your cluster to handle the load better, or reduce the number of concurrent tasks. Additionally, ensure that your network is stable and fast enough to handle the data transfer.
This guide will help you check for common problems that cause the log ” [” + job.getId() + “] Timed out waiting for killed job ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “[” + job.getId() + “] Timed out waiting for killed job” classname is AutodetectCommunicator.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
if (awaitCompletion) {
try {
autodetectResultProcessor.awaitCompletion();
} catch (TimeoutException e) {
logger.warn(() -> "[" + job.getId() + "] Timed out waiting for killed job"; e);
}
}
} finally {
if (finish) {
onFinishHandler.accept(null; finalizeJob);
[ratemypost]
