# (no subject)

**URL:** <https://discuss.elastic.co/t/no-subject/3526>\
**Category:** Elasticsearch\
**Created:** [November 5, 2010, 2:17pm UTC](https://discuss.elastic.co/t/no-subject/3526 "2010-11-05T14:17:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kenneth\_Loafman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kenneth_loafman/32/2224_2.png) [@Kenneth\_Loafman](https://discuss.elastic.co/u/Kenneth_Loafman)\
**Post date:** [November 5, 2010, 2:17pm UTC](https://discuss.elastic.co/t/no-subject/3526/1 "2010-11-05T14:17:22Z")

</div>

Hi,

We have two clusters on 0.12 that both go to yellow when there is a  
transient network outage. This happens overnight mostly, perhaps some form  
of maintenance on the cloud providers part. The cluster never recovers the  
connection and both require a restart of their secondary nodes. Is there a  
setting I need to change in order to keep this from happening? The relevant  
part of the config file is:

cloud:

> ```
> aws:
> access_key: munged
> secret_key: munged
> 
> ```
> 
> gateway:  
> type: s3  
> s3:  
> bucket: munged  
> recover\_after\_nodes: 2
> 
> network:  
> host: host0
> 
> discovery.zen.ping.multicast:  
> enabled: false
> 
> discovery.zen.ping.unicast:  
> hosts: ["host0:9300","host1:9300"]

...Thanks,  
...Ken

---

<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, 4:17am UTC](https://discuss.elastic.co/t/no-subject/3526/2 "2017-07-06T04:17:04Z")

</div>