# Elasticsearch recovering process took a long time
**URL:** https://discuss.elastic.co/t/elasticsearch-recovering-process-took-a-long-time/18774
**Category:** Elasticsearch
**Created:** [July 21, 2014, 8:20pm UTC](https://discuss.elastic.co/t/elasticsearch-recovering-process-took-a-long-time/18774 "2014-07-21T20:20:03Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@silvina](https://discuss.elastic.co/u/silvina)
#### Post date: [July 21, 2014, 8:20pm UTC](https://discuss.elastic.co/t/elasticsearch-recovering-process-took-a-long-time/18774/1 "2014-07-21T20:20:03Z")
Hi,
We are using elasticsearch 0.90.1. We had some problems with the network,
when the network is down (the convergence time is around 40s). Recovering
the elastic after this event took a long time to be available. We have 16
data nodes and 16 shards with 2 replica and the settings:
discovery.zen.minimum\_master\_nodes: 4
gateway.recover\_after\_nodes: 4
gateway.expected\_nodes: 6
Any idea about how to minimize the recovery time?
Is it a good idea to update the version?
What will happen if we increase discovery.zen.fd.ping\_interval and
ping\_timeout settings? Assuming the network is completely off, is there any
way to wait for at least those 40 seconds to start marking servers down?
Does the ping\_timeout ignore the failure to connect to a node?
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).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/a32a0c42-122a-45a3-9c56-8869b4028608%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/a32a0c42-122a-45a3-9c56-8869b4028608%40googlegroups.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@silvina](https://discuss.elastic.co/u/silvina)
#### Post date: [July 21, 2014, 8:28pm UTC](https://discuss.elastic.co/t/elasticsearch-recovering-process-took-a-long-time/18774/2 "2014-07-21T20:28:30Z")
Sorry, the setting discovery.zen.minimum\_master\_nodes is 8
El lunes, 21 de julio de 2014 17:20:03 UTC-3, anivlis escribió:
> Hi,
> We are using elasticsearch 0.90.1. We had some problems with the network,
> when the network is down (the convergence time is around 40s). Recovering
> the elastic after this event took a long time to be available. We have 16
> data nodes and 16 shards with 2 replica and the settings:
>
> discovery.zen.minimum\_master\_nodes: 4
> gateway.recover\_after\_nodes: 4
> gateway.expected\_nodes: 6
>
> Any idea about how to minimize the recovery time?
> Is it a good idea to update the version?
> What will happen if we increase discovery.zen.fd.ping\_interval and
> ping\_timeout settings? Assuming the network is completely off, is there any
> way to wait for at least those 40 seconds to start marking servers down?
> Does the ping\_timeout ignore the failure to connect to a node?
>
> 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).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/7997de22-b421-4f7c-ae7f-e001dbfef618%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/7997de22-b421-4f7c-ae7f-e001dbfef618%40googlegroups.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@Ivan](https://discuss.elastic.co/u/Ivan)
#### Post date: [July 21, 2014, 8:44pm UTC](https://discuss.elastic.co/t/elasticsearch-recovering-process-took-a-long-time/18774/3 "2014-07-21T20:44:54Z")
Recovery is throttled since version 0.90.1
> **[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.
Increase indices.store.throttle.max\_bytes\_per\_sec to a level that is
suitable for your environment. Since IO should be the main bottleneck, the
setting could vary greatly depending on SSD, platter disk or shared storage.
--
Ivan
On Mon, Jul 21, 2014 at 1:28 PM, anivlis [svlucero@gmail.com](mailto:svlucero@gmail.com) wrote:
> Sorry, the setting discovery.zen.minimum\_master\_nodes is 8
>
> El lunes, 21 de julio de 2014 17:20:03 UTC-3, anivlis escribió:
>
> > Hi,
> > We are using elasticsearch 0.90.1. We had some problems with the network,
> > when the network is down (the convergence time is around 40s). Recovering
> > the elastic after this event took a long time to be available. We have 16
> > data nodes and 16 shards with 2 replica and the settings:
> >
> > discovery.zen.minimum\_master\_nodes: 4
> > gateway.recover\_after\_nodes: 4
> > gateway.expected\_nodes: 6
> >
> > Any idea about how to minimize the recovery time?
> > Is it a good idea to update the version?
> > What will happen if we increase discovery.zen.fd.ping\_interval and
> > ping\_timeout settings? Assuming the network is completely off, is there any
> > way to wait for at least those 40 seconds to start marking servers down?
> > Does the ping\_timeout ignore the failure to connect to a node?
> >
> > 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).
> To view this discussion on the web visit
> [https://groups.google.com/d/msgid/elasticsearch/7997de22-b421-4f7c-ae7f-e001dbfef618%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/7997de22-b421-4f7c-ae7f-e001dbfef618%40googlegroups.com)
> [https://groups.google.com/d/msgid/elasticsearch/7997de22-b421-4f7c-ae7f-e001dbfef618%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/7997de22-b421-4f7c-ae7f-e001dbfef618%40googlegroups.com?utm_medium=email&utm_source=footer)
> .
>
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
--
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).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQACJs%3Dzuu4gjYTvcKpF%2BSgv\_1UkYZw%3DC0G8FkY1meAg-Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQACJs%3Dzuu4gjYTvcKpF%2BSgv_1UkYZw%3DC0G8FkY1meAg-Q%40mail.gmail.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 1:14am UTC](https://discuss.elastic.co/t/elasticsearch-recovering-process-took-a-long-time/18774/4 "2017-07-06T01:14:25Z")