# Mapping corruption after data replication or reallocation

**URL:** <https://discuss.elastic.co/t/mapping-corruption-after-data-replication-or-reallocation/52351>\
**Category:** Elasticsearch\
**Created:** [June 9, 2016, 3:53pm UTC](https://discuss.elastic.co/t/mapping-corruption-after-data-replication-or-reallocation/52351 "2016-06-09T15:53:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ssorlin](https://avatars.discourse-cdn.com/v4/letter/s/a9a28c/32.png) [@ssorlin](https://discuss.elastic.co/u/ssorlin)\
**Post date:** [June 9, 2016, 3:53pm UTC](https://discuss.elastic.co/t/mapping-corruption-after-data-replication-or-reallocation/52351/1 "2016-06-09T15:53:50Z")

</div>

Hi,

For the second time, restarting sequentially the two shards of a same cluster results in an incorrect mapping for one a my index. The special "\_source" field is defined in the resulting mapping as a "normal" field, indexed as a standard string... The consequences are these ones : new indexation are bad (no data, only \_id, and some technical fields), all queries using "\_source" filtering fails.

I have a cluster with two shards. One index is defined with one shard and one replica. I sequentially restart shards, waiting a green status between first and second restart.

Elasticsearch version is 2.0.0.

Can I have help on this issue?

Thanks

---

<div class="post-metadata">

**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, 10:44pm UTC](https://discuss.elastic.co/t/mapping-corruption-after-data-replication-or-reallocation/52351/2 "2017-07-05T22:44:59Z")

</div>