Mapping conflict after upgrading from 6.4.0 to 6.5.2

I've recently updated my Elastic Stack from 6.4.0 to 6.5.1 and then 6.5.2 and now I have some mapping conflicts.

For the most part everything went well when using the rolling upgrade documentation. I did experience some issues when upgrading from 6.4.0 to 6.5.1 where I had to delete some indices:

curl -XDELETE 'http://localhost:9200/.kibana_2'
curl -XDELETE 'http://localhost:9200/.kibana_1'
curl -XDELETE 'http://localhost:9200/.kibana_2'

Now that I'm on 6.5.2, I'm noticing the following issue on my winlogbeat-* indices:

Mapping conflict

4 fields are defined as several types (string, integer, etc) across the indices that match this pattern. You may still be able to use these conflict fields in parts of Kibana, but they will be unavailable for functions that require Kibana to know their type. Correcting this issue will require reindexing your data.

Now, there's a few things that I noticed about my indices, which is probably the reason for this issue. Some indices have multiple versions for the same date, which seems normal given I upgraded during and the metadata was associated to the new index:


Is this the issue? Will reindexing allow these indices to become one index based on the time metadata?


I'm a little bit stuck on how to proceed from here. Any help or guidance is greatly appreciated.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.