No version match ; default to – How to solve related issues

Average Read Time

2 Mins

No version match ; default to – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run 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 ” 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 and version.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “No version match {}; default to {}” classname is Lucene.java.
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;
        }
    }

    /**




 

Run the Check-Up to get customized insights on your system:

Analyze your cluster

Skip to content