# How to fix setting "indices.recovery.max\_bytes\_per\_sec" in splitted cluster?

**URL:** <https://discuss.elastic.co/t/how-to-fix-setting-indices-recovery-max-bytes-per-sec-in-splitted-cluster/176455>\
**Category:** Elasticsearch\
**Created:** [April 11, 2019, 4:30pm UTC](https://discuss.elastic.co/t/how-to-fix-setting-indices-recovery-max-bytes-per-sec-in-splitted-cluster/176455 "2019-04-11T16:30:03Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rmsys](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rmsys/32/40932_2.png) [@rmsys](https://discuss.elastic.co/u/rmsys)\
**Post date:** [April 11, 2019, 4:30pm UTC](https://discuss.elastic.co/t/how-to-fix-setting-indices-recovery-max-bytes-per-sec-in-splitted-cluster/176455/1 "2019-04-11T16:30:03Z")

</div>

Hi guys!

I have a cluster (v5.6.4) with nodes in most default settings, and this settings works in cluster

9 nodes [all master eligible, ingest: (default=true), client: (default=true) and data: (default=true)]

and with this config settings in all too:

> cluster.routing.allocation.node\_initial\_primaries\_recoveries: 2  
> cluster.routing.allocation.node\_concurrent\_recoveries: 2  
> indices.recovery.max\_bytes\_per\_sec: 10mb

But, in my new cluster env (v5.6.16) with master, client, data and kibana in separated instances this configs are not to be applied.

I put the config in all nodes, but nothing...

What is wrong? Only dynamic?

---

<div class="post-metadata">

**Author:** ![nhat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nhat/32/22170_2.png) [@nhat](https://discuss.elastic.co/u/nhat)\
**Post date:** [April 11, 2019, 6:03pm UTC](https://discuss.elastic.co/t/how-to-fix-setting-indices-recovery-max-bytes-per-sec-in-splitted-cluster/176455/2 "2019-04-11T18:03:34Z")

</div>

Can you provide your cluster setting including the defaults? `GET /_cluster/settings?include_defaults=true`?

---

<div class="post-metadata">

**Author:** ![nhat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nhat/32/22170_2.png) [@nhat](https://discuss.elastic.co/u/nhat)\
**Post date:** [April 11, 2019, 10:29pm UTC](https://discuss.elastic.co/t/how-to-fix-setting-indices-recovery-max-bytes-per-sec-in-splitted-cluster/176455/4 "2019-04-11T22:29:02Z")

</div>

@rmsys The content was truncated. Can you make it as a gist?

---

<div class="post-metadata">

**Author:** ![rmsys](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rmsys/32/40932_2.png) [@rmsys](https://discuss.elastic.co/u/rmsys)\
**Post date:** [April 17, 2019, 1:45am UTC](https://discuss.elastic.co/t/how-to-fix-setting-indices-recovery-max-bytes-per-sec-in-splitted-cluster/176455/7 "2019-04-17T01:45:40Z")

</div>

bump

---

<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:** [May 15, 2019, 1:45am UTC](https://discuss.elastic.co/t/how-to-fix-setting-indices-recovery-max-bytes-per-sec-in-splitted-cluster/176455/8 "2019-05-15T01:45:43Z")

</div>

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