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

Get an Elasticsearch Check-Up

Check if your ES issues are caused from misconfigured settings
(Free 2 min process)

Check-Up

Last update: Jan-20

Elasticsearch Error Guide In Page Navigation (click to jump) :

Troubleshooting Background – start here to get the full picture       
Related Issues – selected resources on related issues  
Log Context – usefull for experts
About Opster – offering a diffrent approach to troubleshoot Elasticsearch

Check Your Elasticsearch Settings for Painfull Mistakes 


Troubleshooting background

To troubleshoot Elasticsearch log “No version match ; default to” it’s important to know common problems related to Elasticsearch concepts: lucene, version. See below-detailed explanations complete with common problems, examples and useful tips.

Lucene and Elasticsearch

What it is 

Lucene or Apache Lucene is an open-source Java library used as a search engine. Elasticsearch is built on top of Lucene. 

Elasticsearch converts Lucene into a distributed system/search engine for scaling horizontally. Elasticsearch also provides other features like thread-pool, queues, node/cluster monitoring API, data monitoring API, Cluster management, etc. In short , Elasticsearch extends Lucene and provides additional features in addition to it.

Elasticsearch hosts data on data nodes. Each data node hosts one or more indices , and each index is divided into shards with each shard holding part of the index data. From technical and operative perspectives, each shard created in Elasticsearch is a separate Lucene instance or process. Therefore, this concept is of significant importance when attempting to understand elasticsearch internals , indices and shards.

Notes and Good Things to Know:
  • When an index is created in ElasticSearch it is divided into one or more primary shards for scaling the data and splitting it into multiple nodes/instances. The concept of Lucene is relevant here when you are going to decide the number of shards for your index. Too many shards will result in too many Lucene instances, which will consume resources and damage performance.

  • It takes proper planning to decide the number of primary shards for your index , taking into account the index size , max growth , and the number of data nodes.

  • Previous versions of Elasticsearch defaulted to creating five shards per index. Starting with 7.0.0, the default is now one shard per index.


To help troubleshoot related issues we have gathered selected Q&A from the community and issues from Github , please review the following for further information :

1. Github Issue Number 6441  

2. Elasticsearchillegalargumentexcepti      


Log Context

Log ”No version match ; default to” classname is Lucene.java
We have extracted the following from Elasticsearch source code to get 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;
        }
    }

    /**






About Opster

Incorporating deep knowledge and broad history of Elasticsearch issues. Opster’s solution identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to manage, troubleshoot and prevent issues

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster

Did this page help you?