Mapper conflict


I updated my ES v1.5 to 2.4 and I am getting so many errors about mapper conflicts. I would like to know if it is possible to change the mapper field of every index before starting the elasticsearch service or ignore all the data that has errors in other to get elasticsearch up.


Error Example:
Exception in thread "main" java.lang.IllegalStateException: unable to upgrade the mappings for the index [wordlist], reason: [Mapper for [_id] conflicts with existing mapping in other types:
[mapper [_id] has different [index] values]]
Likely root cause: java.lang.IllegalArgumentException: Mapper for [_id] conflicts with existing mapping in other types:
[mapper [_id] has different [index] values]
at org.elasticsearch.index.mapper.FieldTypeLookup.checkCompatibility(
at org.elasticsearch.index.mapper.FieldTypeLookup.copyAndAddAll(
at org.elasticsearch.index.mapper.MapperService.merge(
at org.elasticsearch.index.mapper.MapperService.merge(
at org.elasticsearch.cluster.metadata.MetaDataIndexUpgradeService.checkMappingsCompatibility(
at org.elasticsearch.cluster.metadata.MetaDataIndexUpgradeService.upgradeIndexMetaData(
at org.elasticsearch.gateway.GatewayMetaState.pre20Upgrade(
at org.elasticsearch.gateway.GatewayMetaState.(
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(
at java.lang.reflect.Constructor.newInstance(
at <<>>
at org.elasticsearch.node.Node.(
at org.elasticsearch.node.Node.(
at org.elasticsearch.bootstrap.Bootstrap.setup(
at org.elasticsearch.bootstrap.Bootstrap.init(
at org.elasticsearch.bootstrap.Elasticsearch.main(

(Mark Walkom) #2

You should read


I can not change any mapping because the service is down and the link that you provided does not show a solution.


I removed all the docs located in /var/lib/elasticsearch/YOUR_NODE/nodes/. Now my Es is up

(system) #5