# Poor performance upgrading from 1.4.2 to Elasticsearch 2.3.4

**URL:** <https://discuss.elastic.co/t/poor-performance-upgrading-from-1-4-2-to-elasticsearch-2-3-4/57738>\
**Category:** Elasticsearch\
**Created:** [August 10, 2016, 7:28pm UTC](https://discuss.elastic.co/t/poor-performance-upgrading-from-1-4-2-to-elasticsearch-2-3-4/57738 "2016-08-10T19:28:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![deepakhj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/deepakhj/32/11313_2.png) [@deepakhj](https://discuss.elastic.co/u/deepakhj)\
**Post date:** [August 10, 2016, 7:28pm UTC](https://discuss.elastic.co/t/poor-performance-upgrading-from-1-4-2-to-elasticsearch-2-3-4/57738/1 "2016-08-10T19:28:01Z")

</div>

We are trying to upgrade from 1.4.2 to 2.3.4.

Both clusters are sized the same  
3 masters  
15 data nodes (c3.8xlarge) 64GB 32cores 2 \* 320GB SSD 10Gbit ethernet

Our load average on the current cluster is anywhere from 10-15 and when we tried 2.3.4 it went up to 40.

We have 4 indexes  
24GB 15 shards 1 replica  
1GB 15 shards 2 replica  
1GB 15 shards 2 replica  
83GFB 25 shards 2 replica

Query

> <https://gist.github.com/deepakhj/2fa12b20b1d51312ec9e42d2654d0a8b>

Profile

> <https://gist.github.com/deepakhj/7b85694d74514a06e5a5f4aecda4b4cd>

Hot Threads

> <https://gist.github.com/deepakhj/df8bcbdb1568039501c4feb0f76fbeb3>

---

<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:28pm UTC](https://discuss.elastic.co/t/poor-performance-upgrading-from-1-4-2-to-elasticsearch-2-3-4/57738/2 "2017-07-05T22:28:40Z")

</div>

Closed on July 5, 2017, 10:28pm UTC