search

elastic / elasticsearch-migration

This plugin will help you to check whether you can upgrade directly to the next major version of Elasticsearch, or whether you need to make changes to your data and cluster before doing so.
290 stars 32 forks source link

Migration tool all green, but issues with mapping after upgrade #41

Closed pulberg closed 8 years ago

pulberg commented 8 years ago

I ran the migration tool on a test cluster, all came back green. When attempting to start ES after the upgrade I get this - 

Exception in thread "main" java.lang.IllegalStateException: unable to upgrade the mappings for the index [bp_nfl_concussion_v0000001], reason: [Mapper for [interaction] conflicts with existing mapping in other types[mapper [interaction.author.username] has different [index] values, mapper [interaction.author.username] has different [analyzer], mapper [interaction.author.avatar] has different [index] values, mapper [interaction.author.avatar] has different [analyzer], mapper [interaction.author.link] has different [index] values, mapper [interaction.author.link] has different [analyzer], mapper [interaction.hashtags] has different [index] values, mapper [interaction.hashtags] has different [analyzer], mapper [interaction.created_at] of different type, current_type [string], merged_type [date], mapper [interaction.content] has different [analyzer], mapper [interaction.type] has different [index] values, mapper [interaction.type] has different [analyzer], mapper [interaction.link] has different [index] values, mapper [interaction.link] has different [analyzer], mapper [interaction.received_at] of different type, current_type [double], merged_type [date]]]
Likely root cause: java.lang.IllegalArgumentException: Mapper for [interaction] conflicts with existing mapping in other types[mapper [interaction.author.username] has different [index] values, mapper [interaction.author.username] has different [analyzer], mapper [interaction.author.avatar] has different [index] values, mapper [interaction.author.avatar] has different [analyzer], mapper [interaction.author.link] has different [index] values, mapper [interaction.author.link] has different [analyzer], mapper [interaction.hashtags] has different [index] values, mapper [interaction.hashtags] has different [analyzer], mapper [interaction.created_at] of different type, current_type [string], merged_type [date], mapper [interaction.content] has different [analyzer], mapper [interaction.type] has different [index] values, mapper [interaction.type] has different [analyzer], mapper [interaction.link] has different [index] values, mapper [interaction.link] has different [analyzer], mapper [interaction.received_at] of different type, current_type [double], merged_type [date]]
clintongormley commented 8 years ago

Hi @pulberg

Please could you upload the output from:

GET bp_nfl_concussion_v0000001/_mapping

thanks

pulberg commented 8 years ago

Well, ES won't start (because of the previous error), so i can't run any commands.

clintongormley commented 8 years ago

@pulberg yes, you need to run it from your 1.x server.

pulberg commented 8 years ago

Maybe i'm missing something, but this is just a 1 node test cluster, there is no "1.x server" any longer.

clintongormley commented 8 years ago

@pulberg the only way to debug this is to see what info was in your 1.x cluster (or single node test server) and then compare it to the messages that you saw when upgrading to 2.0, so we can figure it what is missing :)

clintongormley commented 8 years ago

No more feedback. Closing