# Replica shards of newly created indices remain UNASSIGNED

**URL:** <https://discuss.elastic.co/t/replica-shards-of-newly-created-indices-remain-unassigned/379459>\
**Category:** Elasticsearch\
**Created:** [June 25, 2025, 6:26am UTC](https://discuss.elastic.co/t/replica-shards-of-newly-created-indices-remain-unassigned/379459 "2025-06-25T06:26:07Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Tortoise](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tortoise/32/147587_2.png) [@Tortoise](https://discuss.elastic.co/u/Tortoise)\
**Post date:** [June 25, 2025, 6:34am UTC](https://discuss.elastic.co/t/replica-shards-of-newly-created-indices-remain-unassigned/379459/2 "2025-06-25T06:34:25Z")

</div>

Hello @onel

Welcome to the community!!

Your elastic version is 8.14.3 , could you please share below information ?

1. Total number of data nodes in your cluster?
2. Index settings (primary + replicas) for this index ?

I found one blog related to similar issue :

> [@Unassigned replica shards with reason as INDEX\_CREATED](https://discuss.elastic.co/t/unassigned-replica-shards-with-reason-as-index-created/237845/4):
>
> hey @Vinayak_Sapre after i made changes for total\_shards\_per\_node, still out of 14 shards, one replica shard remains unassigned after index rollover. this is not happening after every rollover, but happening frequently! "6" : [ { "state" : "STARTED", "primary" : true, "node" : "xxxxxxxxxxxxxxxx", "relocating\_node" : null, "shard" : 6, "index" : "pm2-logs-2020.06.23-000172", "allocati…

Thanks!!

---

_[View the full topic](https://discuss.elastic.co/t/replica-shards-of-newly-created-indices-remain-unassigned/379459)._