# Elasticsearch 1.7 to 2.4 upgrade and slow indexing **URL:** \ **Category:** Elasticsearch\ **Created:** [October 26, 2017, 11:01pm UTC](https://discuss.elastic.co/t/elasticsearch-1-7-to-2-4-upgrade-and-slow-indexing/105487 "2017-10-26T23:01:38Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![mario12](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mario12/32/29324_2.png) [@mario12](https://discuss.elastic.co/u/mario12)\ **Post date:** [October 26, 2017, 11:01pm UTC](https://discuss.elastic.co/t/elasticsearch-1-7-to-2-4-upgrade-and-slow-indexing/105487/1 "2017-10-26T23:01:38Z")
We recently upgraded elasticsearch 1.7 to 2.4 . Our batch indexing used to take 20 ms before upgrade. After upgrade it’s taking 500-800 ms. Please let me know if there is known issue with es 2.4 or if there is anything that can be performed to speed up the indexing. Our batch size is 1000. ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [October 27, 2017, 3:32pm UTC](https://discuss.elastic.co/t/elasticsearch-1-7-to-2-4-upgrade-and-slow-indexing/105487/2 "2017-10-27T15:32:47Z")
There was a change in Elasticsearch 2.0 to guarantee durability for each document written, that was not there in 1.x - that might be a contributing factor. Apart from that you have not specified any more info, which would be useful to take a look. Versions (ES, JVM), what exactly you are doing. Is it the same load? Is it happening constantly? What about CPU/IO load? Are you using the exact same machines, etc... please take your time and write up a proper report describing your environment, otherwise it is very hard to ehlp. --Alex ---
**Author:** ![mario12](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mario12/32/29324_2.png) [@mario12](https://discuss.elastic.co/u/mario12)\ **Post date:** [October 27, 2017, 3:58pm UTC](https://discuss.elastic.co/t/elasticsearch-1-7-to-2-4-upgrade-and-slow-indexing/105487/3 "2017-10-27T15:58:08Z")
1. ES Version 2.4.4 2. Java version 1.7.0\_80 3. Load havn't changed. 4. We did side by side upgrade (new machines with the same configuration as old ones). 5. It is happening constantly. 6. CPU utilization is less than 15% and we get 25k IOPS and it peaks at 50k. ---
**Author:** ![mario12](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mario12/32/29324_2.png) [@mario12](https://discuss.elastic.co/u/mario12)\ **Post date:** [October 30, 2017, 7:46pm UTC](https://discuss.elastic.co/t/elasticsearch-1-7-to-2-4-upgrade-and-slow-indexing/105487/4 "2017-10-30T19:46:26Z")
@spinscale I updated the required information. ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [November 2, 2017, 9:14am UTC](https://discuss.elastic.co/t/elasticsearch-1-7-to-2-4-upgrade-and-slow-indexing/105487/5 "2017-11-02T09:14:21Z")
have you used async replication, which has been removed in 2.0? ---
**Author:** ![mario12](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mario12/32/29324_2.png) [@mario12](https://discuss.elastic.co/u/mario12)\ **Post date:** [November 9, 2017, 3:21am UTC](https://discuss.elastic.co/t/elasticsearch-1-7-to-2-4-upgrade-and-slow-indexing/105487/6 "2017-11-09T03:21:13Z")
@spinscale We havn't used async replication. We resolved this issue by migrating the indices to different AWS instance type. Thanks for your help. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 7, 2017, 3:21am UTC](https://discuss.elastic.co/t/elasticsearch-1-7-to-2-4-upgrade-and-slow-indexing/105487/7 "2017-12-07T03:21:28Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.