-
Notifications
You must be signed in to change notification settings - Fork 24.6k
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
java.lang.ClassCastException when upgrading to 2.0.0 #14706
Comments
Hi @krisb78 Could you try it without the cloud aws plugin and see if you have the same problem? Also, could you upload the output of thanks |
Hi @clintongormley , Here's my cluster state, I'll try to start the node without cloud-aws and let you know shortly. |
I just ran into the same issue. |
Tried without cloud-aws, but got the same error:
|
@krisb78 Looking at your cluster stats I found that there is an index named |
This indeed is the case - I first created a template with the pattern set to 'hotcoffee_v1*', then started indexing into the 'hotcoffee_v1' index - the cluster (1.7.2) didn't complain. So I have:
and then
I think I have one more index/template set up like that, it never caused me a problem in 1.7.2... Has it changed in 2.0.0 ? |
No (except than the error that you're seeing that expects index and alias names to be unique). So this error needs to be fixed and be able to handle alias and index with the same name. I do think that adding an alias with the same name as the index via index templates should not be allowed. |
Hm, I see your point... I'll check if renaming these aliases fixes the issue. |
agreed! We should |
It looks like trying to create an index and alias with the same name in 2.0 throws the same exception, so this should become clearer with the better exception proposed in #14842 |
It looks like it is impossible to remove an alias with the same name as an index in 1.x:
So I think the only solution is to reindex into a new index, and to delete the old index |
Ok, I think I will be able to get out of this by making sure I don't create new indices with the same names as the aliases defined in my templates. Thanks a lot for looking into this. |
Fixed via #14842 |
Trying to upgrade from 1.7.2 to 2.0.0, following the instructions provided on:
https://www.elastic.co/guide/en/elasticsearch/reference/2.0/restart-upgrade.html
Shut the whole cluster down, removed old plugins, installed the new cloud-aws plugin.
When starting the first master node with 2.0.0 installed, I'm getting:
Full log:
The text was updated successfully, but these errors were encountered: