# ES 6.2.4 Impact of a higher concurrent recovery settings
**URL:** https://discuss.elastic.co/t/es-6-2-4-impact-of-a-higher-concurrent-recovery-settings/134340
**Category:** Elasticsearch
**Created:** [June 3, 2018, 10:13pm UTC](https://discuss.elastic.co/t/es-6-2-4-impact-of-a-higher-concurrent-recovery-settings/134340 "2018-06-03T22:13:47Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@ld\_pvl](https://discuss.elastic.co/u/ld_pvl)
#### Post date: [June 3, 2018, 10:13pm UTC](https://discuss.elastic.co/t/es-6-2-4-impact-of-a-higher-concurrent-recovery-settings/134340/1 "2018-06-03T22:13:47Z")
Hi Team,
What is the impact of setting a higher value for [concurrent recoveries](https://www.elastic.co/guide/en/elasticsearch/reference/current/shards-allocation.html#_shard_allocation_settings) such as `cluster.routing.allocation.node_concurrent_recoveries` and `cluster.routing.allocation.node_initial_primaries_recoveries` for the cluster?
Or in other words, what should I consider when choosing to set a higher value for the above settings - i.e. number of cores, memory, number of shards in the cluster etc? So that I can choose a sensible value.
I would like to increase these values to speed up the recovery process of the cluster because the nodes in my cluster hold a lot of shards and the recovery process could be slow sometimes. I read up somewhere that increasing this helps with recovery because I saw from `GET _cluster/allocation/explain?pretty` that recovery was throttled due to this `reached the limit of incoming shard recoveries`.
Cheers,
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 1, 2018, 10:26pm UTC](https://discuss.elastic.co/t/es-6-2-4-impact-of-a-higher-concurrent-recovery-settings/134340/2 "2018-07-01T22:26:18Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.