Aliases swap from to response was not acknowledged – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.8-8.9

Briefly, this error occurs when Elasticsearch does not acknowledge the swapping of aliases. This could be due to a network issue, a timeout, or a problem with the Elasticsearch cluster. To resolve this issue, you can try the following: 1) Check the network connection and ensure that the Elasticsearch cluster is running properly. 2) Increase the timeout value to allow more time for the operation to complete. 3) Check the Elasticsearch logs for any errors or warnings that might indicate what’s causing the problem. 4) Retry the operation, as temporary issues can sometimes cause this error.

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

Log Context

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


        client.admin().indices().aliases(aliasesRequest; ActionListener.wrap(response -> {
            if (response.isAcknowledged() == false) {
                logger.warn("aliases swap from [{}] to [{}] response was not acknowledged"; sourceIndexName; targetIndex);
        }; listener::onFailure));


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?