hello We haven’t experienced this issue before, but recently we noticed that the primary shards of rollover-created indices are allocated normally, while the replica shards always remain in an UNASSIGNED state. We created a test index to verify this, and the same issue occurred—only the replica sha…

[image] onel: Our Elasticsearch cluster is running version 8.14.3. Can you reproduce this in 8.18.3? I have a hunch this may be something that got fixed in the last year or so since 8.14 was released.

Replica shards of newly created indices remain UNASSIGNED

Elastic Stack Elasticsearch

Tortoise June 25, 2025, 6:34am 2

Hello @onel

Welcome to the community!!

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

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

I found one blog related to similar issue :

Thanks!!

Topic		Replies	Views
Newly created index has unallocated shards Elasticsearch	16	1561	January 27, 2017
Unassigned replica shards after creation of an index, even though there is enough space Elasticsearch	2	2971	September 27, 2017
Getting occasional unassigned replica shards Elasticsearch	2	430	July 6, 2017
One replica shard will not allocate Elasticsearch	3	817	May 15, 2017
Unassigned replica shards with reason as INDEX_CREATED Elasticsearch	5	9871	July 22, 2020

Replica shards of newly created indices remain UNASSIGNED

Related topics