No version match default to – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.1

Briefly, this error occurs when Elasticsearch cannot find a matching version for the default one specified in the configuration or during a version upgrade. This could be due to incorrect version specification or unavailability of the specified version. To resolve this, ensure that the correct version is specified in the configuration file. If you’re upgrading, make sure the new version is correctly installed and available. Also, check for any compatibility issues between the versions. If the problem persists, consider reinstalling Elasticsearch or reverting to a previous stable version.

This guide will help you check for common problems that cause the log ” no version match {}; default to {} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: lucene, version.

Log Context

Log “no version match {}; default to {}” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            return defaultVersion;
        try {
            return Version.parse(version);
        } catch (ParseException e) {
            logger.warn(() -> new ParameterizedMessage("no version match {}; default to {}"; version; defaultVersion); e);
            return defaultVersion;