# Issue of the upgrade from elasticsearch 1.6 to 2.0 **URL:** \ **Category:** Elasticsearch\ **Created:** [November 24, 2015, 9:12am UTC](https://discuss.elastic.co/t/issue-of-the-upgrade-from-elasticsearch-1-6-to-2-0/35401 "2015-11-24T09:12:52Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![tuankun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tuankun/32/8590_2.png) [@tuankun](https://discuss.elastic.co/u/tuankun)\ **Post date:** [November 24, 2015, 9:12am UTC](https://discuss.elastic.co/t/issue-of-the-upgrade-from-elasticsearch-1-6-to-2-0/35401/1 "2015-11-24T09:12:52Z")
hello everyone, We have an elasticsearch cluster which includes 3 nodes, elasticsearch 1.6(rpm package) was installed on them,and hold some indices on them. I just updated the es version from 1.6 to 2.0 on the 3 nodes,following the official guide: [https://www.elastic.co/guide/en/elasticsearch/reference/current/restart-upgrade.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/restart-upgrade.html) then I started the elasticsearch serivce,but an error appeared and the services stopped on all the 3 node server: and how can I solve it? thanks. ---------------------NODE1------------------------- [root@NODE1 ~]# Exception in thread "main" java.lang.IllegalStateException: unable to upgrade the mappings for the index [allie\_traceability\_1], reason: [Mapper for [status] conflicts with existing mapping in other types: [mapper [status] cannot be changed from type [int] to [string]]] Likely root cause: java.lang.IllegalArgumentException: Mapper for [status] conflicts with existing mapping in other types: [mapper [status] cannot be changed from type [int] to [string]] at org.elasticsearch.index.mapper.FieldTypeLookup.checkCompatibility(FieldTypeLookup.java:117) at org.elasticsearch.index.mapper.MapperService.checkNewMappersCompatibility(MapperService.java:345) at org.elasticsearch.index.mapper.MapperService.merge(MapperService.java:296) at org.elasticsearch.index.mapper.MapperService.merge(MapperService.java:242) at org.elasticsearch.cluster.metadata.MetaDataIndexUpgradeService.checkMappingsCompatibility(MetaDataIndexUpgradeService.java:329) at org.elasticsearch.cluster.metadata.MetaDataIndexUpgradeService.upgradeIndexMetaData(MetaDataIndexUpgradeService.java:112) at org.elasticsearch.gateway.GatewayMetaState.pre20Upgrade(GatewayMetaState.java:226) at org.elasticsearch.gateway.GatewayMetaState.(GatewayMetaState.java:85) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) .......... ------------------NODE2-------------------- [root@NODE2 indices]# Exception in thread "main" java.lang.IllegalStateException: unable to upgrade the mappings for the index [allie\_traceability\_10], reason: [Mapper for [usn] conflicts with existing mapping in other types: [mapper [usn] has different [index] values, mapper [usn] has different [omit\_norms] values, cannot change from disable to enabled, mapper [usn] has different [analyzer], mapper [usn] is used by multiple types. Set update\_all\_types to true to update [omit\_norms] across all types., mapper [usn] is used by multiple types. Set update\_all\_types to true to update [search\_analyzer] across all types., mapper [usn] is used by multiple types. Set update\_all\_types to true to update [search\_quote\_analyzer] across all types.]] Likely root cause: java.lang.IllegalArgumentException: Mapper for [usn] conflicts with existing mapping in other types: [mapper [usn] has different [index] values, mapper [usn] has different [omit\_norms] values, cannot change from disable to enabled, mapper [usn] has different [analyzer], mapper [usn] is used by multiple types. Set update\_all\_types to true to update [omit\_norms] across all types., mapper [usn] is used by multiple types. Set update\_all\_types to true to update [search\_analyzer] across all types., mapper [usn] is used by multiple types. Set update\_all\_types to true to update [search\_quote\_analyzer] across all types.] at org.elasticsearch.index.mapper.FieldTypeLookup.checkCompatibility(FieldTypeLookup.java:117) at org.elasticsearch.index.mapper.MapperService.checkNewMappersCompatibility(MapperService.java:345) at org.elasticsearch.index.mapper.MapperService.merge(MapperService.java:296) at org.elasticsearch.index.mapper.MapperService.merge(MapperService.java:242) at org.elasticsearch.cluster.metadata.MetaDataIndexUpgradeService.checkMappingsCompatibility(MetaDataIndexUpgradeService.java:329) at org.elasticsearch.cluster.metadata.MetaDataIndexUpgradeService.upgradeIndexMetaData(MetaDataIndexUpgradeService.java:112) at org.elasticsearch.gateway.GatewayMetaState.pre20Upgrade(GatewayMetaState.java:226) at org.elasticsearch.gateway.GatewayMetaState.(GatewayMetaState.java:85) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) ........ -------------------NODE3------------------------ the error is similar to the NODE1 and NODE2. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [November 24, 2015, 9:11pm UTC](https://discuss.elastic.co/t/issue-of-the-upgrade-from-elasticsearch-1-6-to-2-0/35401/2 "2015-11-24T21:11:14Z")
This is why reading breaking changes for major updates is _really important_. See [https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking\_20\_mapping\_changes.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking_20_mapping_changes.html) ---
**Author:** ![tuankun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tuankun/32/8590_2.png) [@tuankun](https://discuss.elastic.co/u/tuankun)\ **Post date:** [November 25, 2015, 1:05am UTC](https://discuss.elastic.co/t/issue-of-the-upgrade-from-elasticsearch-1-6-to-2-0/35401/3 "2015-11-25T01:05:47Z")
thanks so much,we will study it. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:36pm UTC](https://discuss.elastic.co/t/issue-of-the-upgrade-from-elasticsearch-1-6-to-2-0/35401/4 "2017-07-05T23:36:09Z")