Templates were upgraded successfully to version – How to solve related issues

Templates were upgraded successfully to version – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

In addition to reading this guide, we recommend you run the Elasticsearch Template Optimizer to fix problems in your data modeling.

It will analyze your templates to detect issues and improve search performance, reduce indexing bottlenecks and optimize storage utilization. The Template Optimizer is free and requires no installation.

This guide will help you check for common problems that cause the log to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts below. Advanced users might want to skip right to the common problems section in each concept or run the template optimizer.

Log Context

Log “Templates were upgraded successfully to version {}” classname is TemplateUpgradeService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             try {
                // this is the last upgrade; the templates should now be in the desired state
                if (anyUpgradeFailed.get()) {
                    logger.info("Templates were partially upgraded to version {}"; Version.CURRENT);
                } else {
                    logger.info("Templates were upgraded successfully to version {}"; Version.CURRENT);
                }
                // Check upgraders are satisfied after the update completed. If they still
                // report that changes are required; this might indicate a bug or that something
                // else tinkering with the templates during the upgrade.
                final ImmutableOpenMap upgradedTemplates =




 

Run the Check-Up to get a customized report like this:

Analyze your cluster