Dealing with plugin versions that don't match, Elasticsearch failing to start

[martinb3]

We should see if we can figure out a way to detect that plugins and ES are incompatible, maybe by comparing versions on each run, and ensuring they match?

[karmi]

Normally this is left for the user to configure, since I don't think there some infrastructure in Elasticsearch to verify plugin and core compatibility... But that might have changed.

@dadoonet, do we have some infrastructure for checking plugin compability in new versions of Elasticsearch?

[martinb3]

I'm also wondering if we can at least emit a warning, or even just be sure we don't take plugins with us when we change ES versions using chef, forcing new ones to be installed.

[dadoonet]

@karmi No. The only test we have today is by checking if expected Lucene version is the same as what we have running in the node. It's only checked when lucene is added in es-plugin.properties file: https://github.com/elastic/elasticsearch-analysis-icu/blob/master/src/main/resources/es-plugin.properties#L3

[martinb3]

I'm going to close this then, if there's not an easy test. We'll rely on the 2.0.0 ES release where plugins are versioned with ES itself in the repo.