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

Opster Team

Aug-23, Version: 7.9-7.15

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 network issues, insufficient permissions, or a problem with the template itself. To resolve this issue, you can try the following: 1) Check your network connection and ensure Elasticsearch is running properly. 2) Verify that you have the necessary permissions to add a template. 3) Review the template for any errors or inconsistencies. 4) If the problem persists, consider upgrading to a newer 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 [{}] for [{}]; 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 [{}] for [{}]; request was not acknowledged” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                new ActionListener() {
                    public void onResponse(AcknowledgedResponse response) {
                        if (response.isAcknowledged() == false) {
                            logger.error("error adding legacy template [{}] for [{}]; request was not acknowledged";
                                templateName; getOrigin());



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?