# Unassigned shards stays on INITIALIZING

**URL:** <https://discuss.elastic.co/t/unassigned-shards-stays-on-initializing/22513>\
**Category:** Elasticsearch\
**Created:** [March 4, 2015, 1:25pm UTC](https://discuss.elastic.co/t/unassigned-shards-stays-on-initializing/22513 "2015-03-04T13:25:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Abdul\_Mohammed](https://avatars.discourse-cdn.com/v4/letter/a/3be4f8/32.png) [@Abdul\_Mohammed](https://discuss.elastic.co/u/Abdul_Mohammed)\
**Post date:** [March 4, 2015, 1:25pm UTC](https://discuss.elastic.co/t/unassigned-shards-stays-on-initializing/22513/1 "2015-03-04T13:25:08Z")

</div>

Hi,

I have situation where after performing a restart of ES process, the cluster now stays in RED and I cannot manually/forcefully re-route the INITIALIZING shard to fix cluster's state. Is there any way to fix this ?

From my understanding, I am assuming the index name "paas-docs-ucf2c-2015.02.25" has 5 primary shards and 1 replica.

"curl [http://localhost:9200/\_cat/shards?v](http://localhost:9200/_cat/shards?v)"  
paas-docs-ucf2c-2015.02.25 4 p INITIALIZING 10.241.236.54 ucf2b-devops-espublic2  
paas-docs-ucf2c-2015.02.25 4 r UNASSIGNED  
paas-docs-ucf2c-2015.02.25 0 r STARTED 9595924 3gb 10.241.238.234 ucf2b-devops-espublic3  
paas-docs-ucf2c-2015.02.25 0 p STARTED 9595924 3gb 10.241.236.54 ucf2b-devops-espublic2  
paas-docs-ucf2c-2015.02.25 3 r STARTED 9589378 2.9gb 10.241.238.234 ucf2b-devops-espublic3  
paas-docs-ucf2c-2015.02.25 3 p STARTED 9589378 2.9gb 10.241.236.54 ucf2b-devops-espublic2  
paas-docs-ucf2c-2015.02.25 1 r STARTED 9567744 2.9gb 10.241.238.234 ucf2b-devops-espublic3  
paas-docs-ucf2c-2015.02.25 1 p STARTED 9567744 2.9gb 10.241.236.54 ucf2b-devops-espublic2  
paas-docs-ucf2c-2015.02.25 2 r STARTED 9585661 3gb 10.241.238.234 ucf2b-devops-espublic3  
paas-docs-ucf2c-2015.02.25 2 p STARTED 9585661 3gb 10.241.236.54 ucf2b-devops-espublic2

Summary:-  
paas-docs-ucf2c-2015.02.25 Primary Shard [0] & its replica seems OK  
paas-docs-ucf2c-2015.02.25 Primary Shard [1] & its replica seems OK  
paas-docs-ucf2c-2015.02.25 Primary Shard [2] & its replica seems OK  
paas-docs-ucf2c-2015.02.25 Primary Shard [3] & its replica seems OK  
**paas-docs-ucf2c-2015.02.25 Primary Shard [4] seems to be in "INITIALIZING" since many days and due to which its replica is in "UNASSIGNED" state.**

Tailing logs shows below:-

[2015-03-04 08:20:05,588][WARN][cluster.action.shard] [ucf2b-devops-espublic2] [paas-docs-ucf2c-2015.02.25][4] sending failed shard for [paas-docs-ucf2c-2015.02.25][4], node[4aCqtG66SMSymamyBlFufg], [P], s[INITIALIZING], indexUUID [3iztrXA7SFmiW2L8x\_EXDg], reason [Failed to start shard, message [IndexShardGatewayRecoveryException[[paas-docs-ucf2c-2015.02.25][4] **failed to recover shard** ]; nested: TranslogCorruptedException[translog corruption while reading from stream]; nested: ElasticsearchIllegalArgumentException[No version type match [50]]; ]]

Can you please help me to fix this.

Best regards,  
Abdul

---

<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:** [July 6, 2017, 12:28am UTC](https://discuss.elastic.co/t/unassigned-shards-stays-on-initializing/22513/2 "2017-07-06T00:28:37Z")

</div>