# Problems upgrading cluster to ES 2.0

**URL:** <https://discuss.elastic.co/t/problems-upgrading-cluster-to-es-2-0/36355>\
**Category:** Elasticsearch\
**Created:** [December 4, 2015, 8:27am UTC](https://discuss.elastic.co/t/problems-upgrading-cluster-to-es-2-0/36355 "2015-12-04T08:27:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zyg0te](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zyg0te/32/6415_2.png) [@Zyg0te](https://discuss.elastic.co/u/Zyg0te)\
**Post date:** [December 4, 2015, 8:27am UTC](https://discuss.elastic.co/t/problems-upgrading-cluster-to-es-2-0/36355/1 "2015-12-04T08:27:10Z")

</div>

Ive upgraded my 2 node cluster to Elasticsearch 2.0. However, it seems like it's having some issues migrating my data.

```
[2015-12-04 09:12:24,391][WARN][indices.cluster] [olympus-es01] [sendforth] failed to add mapping [user], source [{"user":{"_id":{"store":true,"in dex":"not_analyzed"},"properties":{"credits":{"type":"long"},"date_created":{"type":"date","format":"dateOptionalTime"},"device_id":{"type":"string"},"enable d":{"type":"boolean"},"last_msg_forwarded":{"type":"date","format":"dateOptionalTime"},"msgs_forwarded":{"type":"long"},"path":{"type":"string"},"token":{"ty pe":"string"}}}}]
java.lang.IllegalArgumentException: Mapper for [_id] conflicts with existing mapping in other types:
[mapper [_id] has different [index] values, mapper [_id] has different [store] values]

```

That lead me to this [github issue.](https://github.com/elastic/elasticsearch/issues/13740)

Does anyone have any suggestions on how to get around or resolve that issue?

---

<div class="post-metadata">

**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:** [December 4, 2015, 8:42am UTC](https://discuss.elastic.co/t/problems-upgrading-cluster-to-es-2-0/36355/2 "2015-12-04T08:42:01Z")

</div>

You need to reindex!

Also, make sure you read release notes _before_ upgrading, as you would have caught this one then 🙂

---

<div class="post-metadata">

**Author:** ![Zyg0te](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zyg0te/32/6415_2.png) [@Zyg0te](https://discuss.elastic.co/u/Zyg0te)\
**Post date:** [December 4, 2015, 8:52am UTC](https://discuss.elastic.co/t/problems-upgrading-cluster-to-es-2-0/36355/3 "2015-12-04T08:52:41Z")

</div>

Thanks for the reply. I did read through the release notes but I guess I missed the part about no longer being able to customize \_id.

---

<div class="post-metadata">

**Author:** ![Zyg0te](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zyg0te/32/6415_2.png) [@Zyg0te](https://discuss.elastic.co/u/Zyg0te)\
**Post date:** [December 4, 2015, 9:08am UTC](https://discuss.elastic.co/t/problems-upgrading-cluster-to-es-2-0/36355/4 "2015-12-04T09:08:02Z")

</div>

Speaking of which. How exactly would I now reindex the data? Do I have to downgrade to the previous version of elasticsearch, reindex and then upgrade again or can I somehow do this without downgrading?

---

<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, 11:33pm UTC](https://discuss.elastic.co/t/problems-upgrading-cluster-to-es-2-0/36355/5 "2017-07-05T23:33:35Z")

</div>