# Slow cluster startup (again)

**URL:** https://discuss.elastic.co/t/slow-cluster-startup-again/13870
**Category:** Elasticsearch
**Created:** [October 7, 2013, 8:53pm UTC](https://discuss.elastic.co/t/slow-cluster-startup-again/13870 "2013-10-07T20:53:47Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Catalin\_Constantin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/catalin_constantin/32/2075_2.png) [@Catalin\_Constantin](https://discuss.elastic.co/u/Catalin_Constantin)
#### Post date: [October 7, 2013, 8:53pm UTC](https://discuss.elastic.co/t/slow-cluster-startup-again/13870/1 "2013-10-07T20:53:47Z")

</div>

Hello,

I have 3 nodes (latest ES 0.90.5).

index.number\_of\_shards = 5  
index.number\_of\_replicas = 2

Gbit internet, SSD drives for /var/lib/elasticsearch.  
I have about 1000 indexes created.  
Total indexes size ~15GB.

How long should the startup of ES take ?  
I keep having status red after hours.  
unassigned\_shards counter goes down really slow.

Currently we have one index per user. Would it help the startup time if we  
make on BIG index and add user\_id as search key ?  
Any other tricks i can do to have a faster startup ?

Thanks,

--  
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: ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)
#### Post date: [October 7, 2013, 9:28pm UTC](https://discuss.elastic.co/t/slow-cluster-startup-again/13870/2 "2013-10-07T21:28:39Z")

</div>

Elasticsearch has been throttling I/O recovery since version 0.90. The  
defaults are fairly low. Trying increasing the  
indices.recovery.max\_bytes\_per\_sec setting. With SSD drives, the setting  
could easily be over 100mb. Mileage may vary.

> **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)**
>
> Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today.

You can also increase the number of shards that are recovered at the same  
time. The default is 2.

Cheers,

Ivan

On Mon, Oct 7, 2013 at 1:53 PM, Catalin Constantin [dazoot@gmail.com](mailto:dazoot@gmail.com) wrote:

> Hello,
> 
> I have 3 nodes (latest ES 0.90.5).
> 
> index.number\_of\_shards = 5  
> index.number\_of\_replicas = 2
> 
> Gbit internet, SSD drives for /var/lib/elasticsearch.  
> I have about 1000 indexes created.  
> Total indexes size ~15GB.
> 
> How long should the startup of ES take ?  
> I keep having status red after hours.  
> unassigned\_shards counter goes down really slow.
> 
> Currently we have one index per user. Would it help the startup time if we  
> make on BIG index and add user\_id as search key ?  
> Any other tricks i can do to have a faster startup ?
> 
> Thanks,
> 
> --  
> 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: ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)
#### Post date: [October 8, 2013, 7:48am UTC](https://discuss.elastic.co/t/slow-cluster-startup-again/13870/3 "2013-10-08T07:48:17Z")

</div>

Yes, it will definitely help if you reduce the number of indices and use  
aliases.

Jörg  
Am 07.10.2013 22:53 schrieb "Catalin Constantin" [dazoot@gmail.com](mailto:dazoot@gmail.com):

> Hello,
> 
> I have 3 nodes (latest ES 0.90.5).
> 
> index.number\_of\_shards = 5  
> index.number\_of\_replicas = 2
> 
> Gbit internet, SSD drives for /var/lib/elasticsearch.  
> I have about 1000 indexes created.  
> Total indexes size ~15GB.
> 
> How long should the startup of ES take ?  
> I keep having status red after hours.  
> unassigned\_shards counter goes down really slow.
> 
> Currently we have one index per user. Would it help the startup time if we  
> make on BIG index and add user\_id as search key ?  
> Any other tricks i can do to have a faster startup ?
> 
> Thanks,
> 
> --  
> 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: ![Catalin\_Constantin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/catalin_constantin/32/2075_2.png) [@Catalin\_Constantin](https://discuss.elastic.co/u/Catalin_Constantin)
#### Post date: [October 8, 2013, 8:08am UTC](https://discuss.elastic.co/t/slow-cluster-startup-again/13870/4 "2013-10-08T08:08:55Z")

</div>

What about search speed ? Will it be affected ?  
There will be a huge index with millions of documents.

Is this slow startup problem considered an issue ?  
Will it be fixed in the future releases ?

While the cluster state is RED, no write operations can be made to it.  
This means "downtime".

Thanks.

--  
Catalin

On Tue, Oct 8, 2013 at 10:48 AM, [joergprante@gmail.com](mailto:joergprante@gmail.com) \<  
[joergprante@gmail.com](mailto:joergprante@gmail.com)\> wrote:

> Yes, it will definitely help if you reduce the number of indices and use  
> aliases.
> 
> Jörg

--  
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: ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)
#### Post date: [October 8, 2013, 9:23am UTC](https://discuss.elastic.co/t/slow-cluster-startup-again/13870/5 "2013-10-08T09:23:23Z")

</div>

This happens because you decided to put hundreds of shards on a single node.

Look at node\_concurrent\_recoveries, the limiting factor so nodes can serve  
requests, even if indices are recovering. If you set this value too high  
you will get high iowait or timeouts.

You can look at your RAM and with 15G, the chance is high you can keep all  
the index files in memory which is very fast.

Jörg  
Am 08.10.2013 10:08 schrieb "Catalin Constantin" [dazoot@gmail.com](mailto:dazoot@gmail.com):

> What about search speed ? Will it be affected ?  
> There will be a huge index with millions of documents.
> 
> Is this slow startup problem considered an issue ?  
> Will it be fixed in the future releases ?
> 
> While the cluster state is RED, no write operations can be made to it.  
> This means "downtime".
> 
> Thanks.
> 
> --  
> Catalin
> 
> On Tue, Oct 8, 2013 at 10:48 AM, [joergprante@gmail.com](mailto:joergprante@gmail.com) \<  
> [joergprante@gmail.com](mailto:joergprante@gmail.com)\> wrote:
> 
> > Yes, it will definitely help if you reduce the number of indices and use  
> > aliases.
> > 
> > Jörg
> > 
> > --  
> > 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: ![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:13am UTC](https://discuss.elastic.co/t/slow-cluster-startup-again/13870/6 "2017-07-06T02:13:22Z")

</div>


