Log No version match ; default to – How To Solve Related Issues

Log No version match ; default to – How To Solve Related Issues

Updated: Jan-20

Elasticsearch Version: 1.7-8.0


To resolve issues causing many log errors you can try our Elasticsearch Check-Up it analyses ES configuration to provide actionable recommendations (no installation required) 

To troubleshoot log “No version match ; default to” it’s important to understand a few problems related to Elasticsearch concepts lucene, version. See bellow important tips and explanations on these concepts

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;


Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Github Issue Number 6441  



About Opster

Opster detects, resolves, optimizes, automates and prevents incidents in Elasticsearch. Opster’s line of products delivers a fundamentally more effective Elasticsearch operation and backs it up with superb production support and consulting.

Find Configuration Errors

Analyze Now