# Prioritize index relocation using wildcards

**URL:** <https://discuss.elastic.co/t/prioritize-index-relocation-using-wildcards/66598>\
**Category:** Elasticsearch\
**Created:** [November 18, 2016, 10:23pm UTC](https://discuss.elastic.co/t/prioritize-index-relocation-using-wildcards/66598 "2016-11-18T22:23:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![stecino](https://avatars.discourse-cdn.com/v4/letter/s/ea666f/32.png) [@stecino](https://discuss.elastic.co/u/stecino)\
**Post date:** [November 18, 2016, 10:23pm UTC](https://discuss.elastic.co/t/prioritize-index-relocation-using-wildcards/66598/1 "2016-11-18T22:23:05Z")

</div>

Looking into this [https://www.elastic.co/guide/en/elasticsearch/reference/2.3/recovery-prioritization.html](https://www.elastic.co/guide/en/elasticsearch/reference/2.3/recovery-prioritization.html)

Is there a way to use wildcards instead when using prioritization? Also, can I set multiple indices to same prioritization value, if that's the case how will it be handled?

This is what I have setup:

cluster.routing.allocation.node\_initial\_primaries\_recoveries: 4  
cluster.routing.allocation.node\_concurrent\_recoveries: 2  
indices.recovery.max\_bytes\_per\_sec: 20mb  
indices.recovery.concurrent\_streams: 5

Is this optimal, or what would be suggested for things to be allocated faster. I have indices that range from a few hundred MB to a few hundred GB

---

<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:** [December 16, 2016, 10:23pm UTC](https://discuss.elastic.co/t/prioritize-index-relocation-using-wildcards/66598/2 "2016-12-16T22:23:28Z")

</div>

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