Job close action was not acknowledged – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch fails to acknowledge the closure of a job. This could be due to network issues, heavy load on the cluster, or a problem with the job itself. To resolve this, you can try the following: 1) Check the cluster’s health and load, and adjust resources if necessary. 2) Investigate the job’s logs for any specific issues. 3) Retry closing the job after some time. 4) If the problem persists, consider restarting the Elasticsearch node.

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

Log Context

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

                        executeAsyncWithOrigin(client; ML_ORIGIN; CloseJobAction.INSTANCE; closeJobRequest; new ActionListener() {

                            public void onResponse(CloseJobAction.Response response) {
                                if (response.isClosed() == false) {
                                    logger.error("[{}] job close action was not acknowledged"; getJobId());

                            public void onFailure(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?