Cannot restore index


(Juan Andres Ramirez) #1

Hello guys,
18 index has been migrated as well from old cluster with ES 1.7 to a new cluster with ES 2.0, but I have a problem with 1 index, here is the message:

 curl -XPOST http://cviadpzl01:9200/_snapshot/my_backup/snapshot_7/_restore?pretty
{
  "error" : {
    "root_cause" : [ {
      "type" : "snapshot_restore_exception",
      "reason" : "[my_backup:snapshot_7] cannot restore index [graylog2_19] because it cannot be upgraded"
    } ],
    "type" : "snapshot_restore_exception",
    "reason" : "[my_backup:snapshot_7] cannot restore index [graylog2_19] because it cannot be upgraded",
    "caused_by" : {
      "type" : "illegal_state_exception",
      "reason" : "unable to upgrade the mappings for the index [graylog2_19], reason: [Mapper for [_timestamp] conflicts with existing mapping in other types:\n[mapper [_timestamp] is used by multiple types. Set update_all_types to true to update [format] across all types.]]",
      "caused_by" : {
        "type" : "illegal_argument_exception",
        "reason" : "Mapper for [_timestamp] conflicts with existing mapping in other types:\n[mapper [_timestamp] is used by multiple types. Set update_all_types to true to update [format] across all types.]"
      }
    }
  },
  "status" : 500
}

Someone knows what I can to do for fix it?.

Thank you.


(Juan Andres Ramirez) #2

OMG, I have 50 index and I have problems with index number 19 to 50 with the same problem....mappings.

Someone knows how to fix it?


(Juan Andres Ramirez) #3

here an other message in logs:

Caused by: java.lang.IllegalArgumentException: Mapper for [_timestamp] conflicts with existing mapping in other types:
[mapper [_timestamp] is used by multiple types. Set update_all_types to true to update [format] 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)

So the problem is with Mapper for _timestamp, someone knows how to fix it?.

Thank you.


(Juan Andres Ramirez) #4

Anyone please?


(Inderjeet Singh) #5

I am having this exact same issue with the @timestamp field when indexing the data/events sent with logstash. More detail to this problem: https://www.elastic.co/blog/great-mapping-refactoring


(system) #6