# Slow index performance after upgrade from 5.6.8 to 6.1.4

**URL:** <https://discuss.elastic.co/t/slow-index-performance-after-upgrade-from-5-6-8-to-6-1-4/146756>\
**Category:** Elasticsearch\
**Created:** [August 30, 2018, 5:40pm UTC](https://discuss.elastic.co/t/slow-index-performance-after-upgrade-from-5-6-8-to-6-1-4/146756 "2018-08-30T17:40:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dltu](https://avatars.discourse-cdn.com/v4/letter/d/f05b48/32.png) [@dltu](https://discuss.elastic.co/u/dltu)\
**Post date:** [August 30, 2018, 5:40pm UTC](https://discuss.elastic.co/t/slow-index-performance-after-upgrade-from-5-6-8-to-6-1-4/146756/1 "2018-08-30T17:40:37Z")

</div>

After upgrade, my cluster become very worst when ingest data.  
With normal status (not ingest), everything ok(cpu, heap, io, network, load.. keep low)  
But with some small ingest continously, cluster become poor perfomance. CPU and heap still keep in low, but load and iowait raise high and not release (iowait about 40, load avg 20, index speed less than 10k/s with 8 datanode cluster). Before upgrade, index speed about 200k/s.  
I don't change any config or amount of data daily. So where I can look to deal with that?  
Log in datanode have many line with 'starting segment upgrade/finished segment upgrade'. Is it hurt my index perfomance? And if yes, how to deal with that?  
Thanks you.

---

<div class="post-metadata">

**Author:** ![jaddison](https://avatars.discourse-cdn.com/v4/letter/j/e5b9ba/32.png) [@jaddison](https://discuss.elastic.co/u/jaddison)\
**Post date:** [September 10, 2018, 4:08am UTC](https://discuss.elastic.co/t/slow-index-performance-after-upgrade-from-5-6-8-to-6-1-4/146756/2 "2018-09-10T04:08:15Z")

</div>

Did you reindex your data from the original 5.6.8 index format to a new index created with ES 6.1.4? Running old version indexes in a newer ES version might be a problem. (I'm not sure on this, but I have to ask)

---

<div class="post-metadata">

**Author:** ![dltu](https://avatars.discourse-cdn.com/v4/letter/d/f05b48/32.png) [@dltu](https://discuss.elastic.co/u/dltu)\
**Post date:** [September 10, 2018, 4:30am UTC](https://discuss.elastic.co/t/slow-index-performance-after-upgrade-from-5-6-8-to-6-1-4/146756/3 "2018-09-10T04:30:10Z")

</div>

Yeah I already reindex all data to new format. But with some restart node, hot shards is not balances across my cluster, then some node are overworkload and I think it must swap current-process different shard continously. So, anyone has some heuristic/strategy/experience with manual/auto routing shards to deal with that?

---

<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:** [October 8, 2018, 4:36am UTC](https://discuss.elastic.co/t/slow-index-performance-after-upgrade-from-5-6-8-to-6-1-4/146756/4 "2018-10-08T04:36:43Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.