# Delay assigning new replica shards

**URL:** <https://discuss.elastic.co/t/delay-assigning-new-replica-shards/361199>\
**Category:** Elasticsearch\
**Created:** [June 10, 2024, 8:59pm UTC](https://discuss.elastic.co/t/delay-assigning-new-replica-shards/361199 "2024-06-10T20:59:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![linkerc](https://avatars.discourse-cdn.com/v4/letter/l/13edae/32.png) [@linkerc](https://discuss.elastic.co/u/linkerc)\
**Post date:** [June 10, 2024, 8:59pm UTC](https://discuss.elastic.co/t/delay-assigning-new-replica-shards/361199/1 "2024-06-10T20:59:52Z")

</div>

Whenever I tweak the following settings.

```auto
PUT _cluster/settings
{
  "persistent": {
    "cluster.routing.allocation.balance.threshold": null,
    "cluster.routing.allocation.cluster_concurrent_rebalance": null,
    "cluster.routing.allocation.node_concurrent_recoveries": null,
    "cluster.routing.allocation.node_concurrent_incoming_recoveries":null,
    "cluster.routing.allocation.node_concurrent_outgoing_recoveries":null
  }
}

```

I've noticed that newly created index will have the replicas in "unassigned" state for a long time until existing rebalancing is finished. Has newer ES releases fix this?  
We are running version 8.10.2.

It seems silly that new shards assignment is in the same queue as rebalancing existing shards.