Log Templates were upgraded successfully to version – How To Solve Related Issues


Log Templates were upgraded successfully to version – How To Solve Related Issues

Opster Team

Jan-20, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Templates were upgraded successfully to version ” 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: cluster, metadata, template, upgrade and version.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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 =




 

Optimize Elasticsearch Performance

Try The Tool