Error adding legacy template request was not acknowledged – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.1-7.17

Briefly, this error occurs when Elasticsearch fails to acknowledge the addition of a legacy template. This could be due to a variety of reasons such as incorrect template syntax, insufficient permissions, or network issues. To resolve this, you can check the syntax of your template, ensure that the user has the necessary permissions to add a template, and verify that your network connection to the Elasticsearch server is stable. Additionally, consider upgrading to the latest version of Elasticsearch as legacy templates are deprecated in newer versions.

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

Log Context

Log “error adding legacy template [{}]; request was not acknowledged” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            executeAsyncWithOrigin(client; ML_ORIGIN; PutComposableIndexTemplateAction.INSTANCE; templateRequest; innerListener);
        } else {
            ActionListener innerListener = ActionListener.wrap(response -> {
                if (response.isAcknowledged() == false) {
                    logger.warn("error adding legacy template [{}]; request was not acknowledged";;
            }; 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?