Cannot start plugin due to incorrect Lucene version plugin . node .

Opster Team

Feb-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 ” Cannot start plugin due to incorrect Lucene version plugin . node . ” 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: lucene, node, plugin and plugins.

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 “cannot start plugin due to incorrect Lucene version: plugin [{}]; node [{}].” classname is PluginsService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             }
        } catch (Throwable t) {
            // We don't have the expected version... Let's fail after.
            logger.debug("exception raised while checking plugin Lucene version."; t);
        }
        logger.error("cannot start plugin due to incorrect Lucene version: plugin [{}]; node [{}].";
                luceneVersion; Constants.LUCENE_MAIN_VERSION);
        return false;
    }
}