# Shards stuck in initializing status for long time

**URL:** <https://discuss.elastic.co/t/shards-stuck-in-initializing-status-for-long-time/10900>\
**Category:** Elasticsearch\
**Created:** [February 26, 2013, 6:48am UTC](https://discuss.elastic.co/t/shards-stuck-in-initializing-status-for-long-time/10900 "2013-02-26T06:48:52Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dong\_Aihua](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dong_aihua/32/2413_2.png) [@Dong\_Aihua](https://discuss.elastic.co/u/Dong_Aihua)\
**Post date:** [February 26, 2013, 6:48am UTC](https://discuss.elastic.co/t/shards-stuck-in-initializing-status-for-long-time/10900/1 "2013-02-26T06:48:52Z")

</div>

Hi, guys:  
I created a new cluster from scratch.  
After the cluster is up, I tried to create some empty indices for example  
index-2013-02-25, index-2013-02-26, index-2013-02-27, index-2013-03-01, etc  
But some shards stuck in initializing status for long time.  
{  
"cluster\_name" : "es-test",  
"status" : "yellow",  
"timed\_out" : false,  
"number\_of\_nodes" : 20,  
"number\_of\_data\_nodes" : 15,  
"active\_primary\_shards" : 105,  
"active\_shards" : 201,  
"relocating\_shards" : 0,  
"initializing\_shards" : 9,  
"unassigned\_shards" : 0  
}  
There is no error log in the logs.

Moreover when I created index-2013-03-02, the cluster became to red.  
{  
"cluster\_name" : "es-test",  
"status" : "red",  
"timed\_out" : false,  
"number\_of\_nodes" : 20,  
"number\_of\_data\_nodes" : 15,  
"active\_primary\_shards" : 119,  
"active\_shards" : 228,  
"relocating\_shards" : 0,  
"initializing\_shards" : 11,  
"unassigned\_shards" : 1  
}

Does anyone know why this happen?  
Thank you very much!

-Regards-  
-Dong Aihua-

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Dong\_Aihua](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dong_aihua/32/2413_2.png) [@Dong\_Aihua](https://discuss.elastic.co/u/Dong_Aihua)\
**Post date:** [February 26, 2013, 7:23am UTC](https://discuss.elastic.co/t/shards-stuck-in-initializing-status-for-long-time/10900/2 "2013-02-26T07:23:36Z")

</div>

By the way, I set the log level to trace, and checked the logs, no error  
logs are shown. but from the logs, I can know some shards are initializing  
and unassigned.

在 2013年2月26日星期二UTC+9下午3时48分52秒，jackiedong写道：

> Hi, guys:  
> I created a new cluster from scratch.  
> After the cluster is up, I tried to create some empty indices for  
> example index-2013-02-25, index-2013-02-26, index-2013-02-27,  
> index-2013-03-01, etc  
> But some shards stuck in initializing status for long time.  
> {  
> "cluster\_name" : "es-test",  
> "status" : "yellow",  
> "timed\_out" : false,  
> "number\_of\_nodes" : 20,  
> "number\_of\_data\_nodes" : 15,  
> "active\_primary\_shards" : 105,  
> "active\_shards" : 201,  
> "relocating\_shards" : 0,  
> "initializing\_shards" : 9,  
> "unassigned\_shards" : 0  
> }  
> There is no error log in the logs.
> 
> Moreover when I created index-2013-03-02, the cluster became to red.  
> {  
> "cluster\_name" : "es-test",  
> "status" : "red",  
> "timed\_out" : false,  
> "number\_of\_nodes" : 20,  
> "number\_of\_data\_nodes" : 15,  
> "active\_primary\_shards" : 119,  
> "active\_shards" : 228,  
> "relocating\_shards" : 0,  
> "initializing\_shards" : 11,  
> "unassigned\_shards" : 1  
> }
> 
> Does anyone know why this happen?  
> Thank you very much!
> 
> -Regards-  
> -Dong Aihua-

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [February 26, 2013, 7:44am UTC](https://discuss.elastic.co/t/shards-stuck-in-initializing-status-for-long-time/10900/3 "2013-02-26T07:44:55Z")

</div>

Did you set anything for your indices or did you use defaults?

Did you modify anyhow elasticsearch.yml?

Is it on a single box?

--  
David 😉  
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 26 févr. 2013 à 08:23, jackiedong [jackiedong168@gmail.com](mailto:jackiedong168@gmail.com) a écrit :

> By the way, I set the log level to trace, and checked the logs, no error logs are shown. but from the logs, I can know some shards are initializing and unassigned.
> 
> 在 2013年2月26日星期二UTC+9下午3时48分52秒，jackiedong写道：
> 
> > Hi, guys:  
> > I created a new cluster from scratch.  
> > After the cluster is up, I tried to create some empty indices for example index-2013-02-25, index-2013-02-26, index-2013-02-27, index-2013-03-01, etc  
> > But some shards stuck in initializing status for long time.  
> > {  
> > "cluster\_name" : "es-test",  
> > "status" : "yellow",  
> > "timed\_out" : false,  
> > "number\_of\_nodes" : 20,  
> > "number\_of\_data\_nodes" : 15,  
> > "active\_primary\_shards" : 105,  
> > "active\_shards" : 201,  
> > "relocating\_shards" : 0,  
> > "initializing\_shards" : 9,  
> > "unassigned\_shards" : 0  
> > }  
> > There is no error log in the logs.
> > 
> > Moreover when I created index-2013-03-02, the cluster became to red.  
> > {  
> > "cluster\_name" : "es-test",  
> > "status" : "red",  
> > "timed\_out" : false,  
> > "number\_of\_nodes" : 20,  
> > "number\_of\_data\_nodes" : 15,  
> > "active\_primary\_shards" : 119,  
> > "active\_shards" : 228,  
> > "relocating\_shards" : 0,  
> > "initializing\_shards" : 11,  
> > "unassigned\_shards" : 1  
> > }
> > 
> > Does anyone know why this happen?  
> > Thank you very much!
> > 
> > -Regards-  
> > -Dong Aihua-  
> > --  
> > You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
> > To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Dong\_Aihua](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dong_aihua/32/2413_2.png) [@Dong\_Aihua](https://discuss.elastic.co/u/Dong_Aihua)\
**Post date:** [February 26, 2013, 8:02am UTC](https://discuss.elastic.co/t/shards-stuck-in-initializing-status-for-long-time/10900/4 "2013-02-26T08:02:36Z")

</div>

I used 20 machines. And I just tried 0.20.4 and 0.20.5, the same problem.  
But for 0.19.11, the problem disappeared. All the empty indices can be  
created successfully instantly even for some strange index names.  
So I guess maybe ES has some bugs for 0.20.4 and 0.20.5.

-Regards-  
-Dong Aihua-

在 2013年2月26日星期二UTC+9下午4时44分55秒，David Pilato写道：

> Did you set anything for your indices or did you use defaults?
> 
> Did you modify anyhow elasticsearch.yml?
> 
> Is it on a single box?
> 
> --  
> David 😉  
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> 
> Le 26 févr. 2013 à 08:23, jackiedong \<[jackie...@gmail.com](mailto:jackie...@gmail.com) \<javascript:\>\>  
> a écrit :
> 
> By the way, I set the log level to trace, and checked the logs, no error  
> logs are shown. but from the logs, I can know some shards are initializing  
> and unassigned.
> 
> 在 2013年2月26日星期二UTC+9下午3时48分52秒，jackiedong写道：
> 
> > Hi, guys:  
> > I created a new cluster from scratch.  
> > After the cluster is up, I tried to create some empty indices for  
> > example index-2013-02-25, index-2013-02-26, index-2013-02-27,  
> > index-2013-03-01, etc  
> > But some shards stuck in initializing status for long time.  
> > {  
> > "cluster\_name" : "es-test",  
> > "status" : "yellow",  
> > "timed\_out" : false,  
> > "number\_of\_nodes" : 20,  
> > "number\_of\_data\_nodes" : 15,  
> > "active\_primary\_shards" : 105,  
> > "active\_shards" : 201,  
> > "relocating\_shards" : 0,  
> > "initializing\_shards" : 9,  
> > "unassigned\_shards" : 0  
> > }  
> > There is no error log in the logs.
> > 
> > Moreover when I created index-2013-03-02, the cluster became to red.  
> > {  
> > "cluster\_name" : "es-test",  
> > "status" : "red",  
> > "timed\_out" : false,  
> > "number\_of\_nodes" : 20,  
> > "number\_of\_data\_nodes" : 15,  
> > "active\_primary\_shards" : 119,  
> > "active\_shards" : 228,  
> > "relocating\_shards" : 0,  
> > "initializing\_shards" : 11,  
> > "unassigned\_shards" : 1  
> > }
> > 
> > Does anyone know why this happen?  
> > Thank you very much!
> > 
> > -Regards-  
> > -Dong Aihua-
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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, 2:49am UTC](https://discuss.elastic.co/t/shards-stuck-in-initializing-status-for-long-time/10900/5 "2017-07-06T02:49:34Z")

</div>


