# Scaling cluster waits on shard initialization

**URL:** <https://discuss.elastic.co/t/scaling-cluster-waits-on-shard-initialization/359863>\
**Category:** Elasticsearch\
**Created:** [May 20, 2024, 7:22pm UTC](https://discuss.elastic.co/t/scaling-cluster-waits-on-shard-initialization/359863 "2024-05-20T19:22:45Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![cvarano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cvarano/32/122082_2.png) [@cvarano](https://discuss.elastic.co/u/cvarano)\
**Post date:** [May 20, 2024, 7:22pm UTC](https://discuss.elastic.co/t/scaling-cluster-waits-on-shard-initialization/359863/1 "2024-05-20T19:22:45Z")

</div>

Hi team!

When scaling up our Elastic-managed cluster, the new nodes do not begin serving search requests until all shards on **all indices** are initialized. I've increased our primary search index's [priority](https://www.elastic.co/guide/en/elasticsearch/reference/current/recovery-prioritization.html) so it's initialized first, but it will still not serve any requests until everything else is initialized. We have a very large enrich index which takes 30-60 minutes to initialize, and is not necessary at all for serving search requests.

Is there a way to have the search index serve requests immediately upon initialization, without waiting on irrelevant indices?

Thank you!