Killing job – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch terminates a task due to excessive resource consumption or when it’s taking too long to complete. This could be due to insufficient system resources, improper configuration, or inefficient queries. To resolve this, you can increase system resources (like memory or CPU), optimize your Elasticsearch configuration for better performance, or improve the efficiency of your queries. Additionally, consider implementing a timeout for long-running tasks to prevent them from consuming too many resources.

This guide will help you check for common problems that cause the log ” [{}] Killing job ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “[{}] Killing job” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        CancellableTask actionTask;
        KillProcessAction.Request request;
        JobTask jobTask;
        ActionListener listener
    ) {"[{}] Killing job"; jobTask.getJobId());; Messages.JOB_AUDIT_KILLING);
        try {
            jobTask.killJob("kill process (api)");
            listener.onResponse(new KillProcessAction.Response(true));
        } catch (Exception e) {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?