Close index request failed to be acknowledged – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.7-8.9

Briefly, this error occurs when Elasticsearch does not receive an acknowledgement for a close index request within a specified timeout period. This could be due to network issues, heavy load on the cluster, or a problem with the specific index. To resolve this issue, you can increase the timeout period, ensure the cluster is not overloaded, or check the health of the index. If the index is corrupted, you may need to restore it from a backup.

This guide will help you check for common problems that cause the log ” close index request failed to be acknowledged ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, index, request.

Log Context

Log “close index request failed to be acknowledged” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (indexMetadata.getState() == IndexMetadata.State.OPEN) {
 CloseIndexRequest closeIndexRequest = new CloseIndexRequest(followerIndex).masterNodeTimeout(TimeValue.MAX_VALUE);
 getClient().admin().indices().close(closeIndexRequest; ActionListener.wrap(r -> {
 if (r.isAcknowledged() == false) {
 throw new ElasticsearchException("close index request failed to be acknowledged");
 }; listener::onFailure));
 } else {


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?