Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
martinb3 opened this issue Jul 6, 2015 · 4 comments

Comments

Projects
None yet
3 participants
@martinb3
Copy link
Contributor

commented Jul 6, 2015

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

This comment has been minimized.

Copy link
Member

commented Jul 6, 2015

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

This comment has been minimized.

Copy link
Contributor Author

commented Jul 6, 2015

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

This comment has been minimized.

Copy link
Member

commented Jul 6, 2015

@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 martinb3 added the enhancement label Jul 7, 2015

@martinb3 martinb3 modified the milestone: 1.1.x release Jul 16, 2015

@martinb3

This comment has been minimized.

Copy link
Contributor Author

commented Oct 16, 2015

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.