# Replica Shard status changing from Initializing to unassigned for long time, finally in unassigned from last few hours

**URL:** <https://discuss.elastic.co/t/replica-shard-status-changing-from-initializing-to-unassigned-for-long-time-finally-in-unassigned-from-last-few-hours/77186>\
**Category:** Elasticsearch\
**Created:** [March 2, 2017, 4:56pm UTC](https://discuss.elastic.co/t/replica-shard-status-changing-from-initializing-to-unassigned-for-long-time-finally-in-unassigned-from-last-few-hours/77186 "2017-03-02T16:56:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nethis](https://avatars.discourse-cdn.com/v4/letter/n/d2c977/32.png) [@nethis](https://discuss.elastic.co/u/nethis)\
**Post date:** [March 2, 2017, 4:56pm UTC](https://discuss.elastic.co/t/replica-shard-status-changing-from-initializing-to-unassigned-for-long-time-finally-in-unassigned-from-last-few-hours/77186/1 "2017-03-02T16:56:23Z")

</div>

Hi,

For an index of 20 shards and 3 replicas, we have around 4 replica shards which are in unassigned state for long time. It is going to Initializing state and coming back to unassigned. Its been few hours and same thing is happening(Intitializing \<-\> UnAssigned)

No errors/messages is seen in the es log file too.

What could be the issue here, please give some pointers here, to resolve this situation.

Primary and other 2 replicas shards status is started, but the size and documents count is not show (\_cat/shards). Please see below

```
customevent 15 p STARTED 52437835 126.3gb 10.158.36.204 ITTESPROD-DATA3 
customevent 15 r STARTED 52437835 126.3gb 10.158.36.211 ITTESPROD-DATA1 
customevent 15 r STARTED 52437835 126.3gb 10.158.36.212 ITTESPROD-DATA2 
customevent 15 r STARTED 52437835 126.3gb 10.158.36.208 ITTESPROD-DATA4 
customevent 11 p STARTED 10.158.36.204 ITTESPROD-DATA3 
customevent 11 r STARTED 10.158.36.212 ITTESPROD-DATA2 
customevent 11 r STARTED 10.158.36.208 ITTESPROD-DATA4 
customevent 11 r INITIALIZING 10.158.36.198 ITTESPROD-DATA5 
customevent 1 p STARTED 51920720 125.5gb 10.158.36.213 ITTESPROD-DATA6 
customevent 1 r STARTED 51920720 125.5gb 10.158.36.204 ITTESPROD-DATA3 
customevent 1 r STARTED 51920720 125.5gb 10.158.36.211 ITTESPROD-DATA1 
customevent 1 r STARTED 51920720 125.5gb 10.158.36.208 ITTESPROD-DATA4 
customevent 13 p STARTED 52446822 126.6gb 10.158.36.204 ITTESPROD-DATA3 
customevent 13 r STARTED 52446822 126.6gb 10.158.36.211 ITTESPROD-DATA1 
customevent 13 r STARTED 52446822 126.6gb 10.158.36.212 ITTESPROD-DATA2 
customevent 13 r STARTED 52446822 126.6gb 10.158.36.208 ITTESPROD-DATA4 
customevent 5 p STARTED 52298680 126.8gb 10.158.36.204 ITTESPROD-DATA3 
customevent 5 r STARTED 52298680 126.8gb 10.158.36.211 ITTESPROD-DATA1 
customevent 5 r STARTED 52298680 126.8gb 10.158.36.212 ITTESPROD-DATA2 
customevent 5 r STARTED 52298680 126.8gb 10.158.36.208 ITTESPROD-DATA4 
customevent 2 p STARTED 52269976 126.7gb 10.158.36.204 ITTESPROD-DATA3 
customevent 2 r STARTED 52269976 126.7gb 10.158.36.211 ITTESPROD-DATA1 
customevent 2 r STARTED 52269976 126.7gb 10.158.36.212 ITTESPROD-DATA2 
customevent 2 r STARTED 52269976 126.7gb 10.158.36.208 ITTESPROD-DATA4 
customevent 19 p STARTED 10.158.36.204 ITTESPROD-DATA3 
customevent 19 r INITIALIZING 10.158.36.211 ITTESPROD-DATA1 
customevent 19 r STARTED 10.158.36.212 ITTESPROD-DATA2 
customevent 19 r STARTED 10.158.36.208 ITTESPROD-DATA4 
customevent 18 p STARTED 10.158.36.204 ITTESPROD-DATA3 
customevent 18 r STARTED 10.158.36.212 ITTESPROD-DATA2 
customevent 18 r STARTED 10.158.36.208 ITTESPROD-DATA4 
customevent 18 r UNASSIGNED                                                  
customevent 16 p STARTED 52363036 127gb 10.158.36.204 ITTESPROD-DATA3 
customevent 16 r STARTED 52363036 127gb 10.158.36.211 ITTESPROD-DATA1
```

---

<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:** [March 30, 2017, 4:56pm UTC](https://discuss.elastic.co/t/replica-shard-status-changing-from-initializing-to-unassigned-for-long-time-finally-in-unassigned-from-last-few-hours/77186/2 "2017-03-30T16:56:24Z")

</div>

Closed on March 30, 2017, 4:56pm UTC

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