# Elasticsearch 6.3.0 shard recovery is slow

**URL:** https://discuss.elastic.co/t/elasticsearch-6-3-0-shard-recovery-is-slow/140940
**Category:** Elasticsearch
**Created:** [July 20, 2018, 3:40pm UTC](https://discuss.elastic.co/t/elasticsearch-6-3-0-shard-recovery-is-slow/140940 "2018-07-20T15:40:19Z")
**Posts on this page:** 1
**Showing post:** 13

<div class="post-metadata">

### Author: ![tomtom1234](https://avatars.discourse-cdn.com/v4/letter/t/c77e96/32.png) [@tomtom1234](https://discuss.elastic.co/u/tomtom1234)
#### Post date: [August 29, 2018, 2:01am UTC](https://discuss.elastic.co/t/elasticsearch-6-3-0-shard-recovery-is-slow/140940/13 "2018-08-29T02:01:43Z")

</div>

I'm currently migrating from a 1.7.x cluster to 6.3.2 and ran into this exact same problem. No matter what i set the indices.recovery.max\_bytes\_per\_sec to, the max throughput is about 11 MB/s. This is a large cluster, with 10Gb ethernet, flash storage, plenty of RAM, CPU, etc so I was equally stumped. Happens I noticed that our previous elasticsearch.yml file had the transport.tcp.compress set to true. I didn't really pay attention to this but i should have. Changing this to false (to disable compression) suddenly results in the bandwidth and recovery performance in line with the indices.recovery.max\_bytes\_per\_sec setting. Is it possible your nodes currently have this set?

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-6-3-0-shard-recovery-is-slow/140940)._