# Elasticsearch upgrade from 1.7.1 to 2.3.2 then create index very slow

**URL:** https://discuss.elastic.co/t/elasticsearch-upgrade-from-1-7-1-to-2-3-2-then-create-index-very-slow/51655
**Category:** Elasticsearch
**Created:** [June 2, 2016, 8:10am UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-from-1-7-1-to-2-3-2-then-create-index-very-slow/51655 "2016-06-02T08:10:25Z")
**Posts on this page:** 1
**Showing post:** 29

<div class="post-metadata">

### Author: ![s1monw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/s1monw/32/3637_2.png) [@s1monw](https://discuss.elastic.co/u/s1monw)
#### Post date: [June 3, 2016, 9:42am UTC](https://discuss.elastic.co/t/elasticsearch-upgrade-from-1-7-1-to-2-3-2-then-create-index-very-slow/51655/29 "2016-06-03T09:42:02Z")

</div>

@tingking23 I wonder if this is due to some difference in how we index things. I wonder if you could go back to your 1.x version and create a new index with all the mappings but don't index documents into it. Then upgrade this to 2.x and run your indexing test? I really wanna know if we changed something in mappings that make these things go nuts? we do a lot of different things based on the version the index was created on.

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-upgrade-from-1-7-1-to-2-3-2-then-create-index-very-slow/51655)._