# Network resiliency - Thumbs up Shay

**URL:** <https://discuss.elastic.co/t/network-resiliency-thumbs-up-shay/8197>\
**Category:** Elasticsearch\
**Created:** [June 22, 2012, 4:16pm UTC](https://discuss.elastic.co/t/network-resiliency-thumbs-up-shay/8197 "2012-06-22T16:16:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jagdeep](https://avatars.discourse-cdn.com/v4/letter/j/ba8739/32.png) [@jagdeep](https://discuss.elastic.co/u/jagdeep)\
**Post date:** [June 22, 2012, 4:16pm UTC](https://discuss.elastic.co/t/network-resiliency-thumbs-up-shay/8197/1 "2012-06-22T16:16:38Z")

</div>

I was facing this issue of network resiliency. I had cluster of  
multiple servers and multiple node, I cut down number of ES nodes  
primarily because network failure resiliency issues. I was tracking  
the discussion on  
[https://groups.google.com/group/elasticsearch/browse\_thread/thread/7c033ea3b9a92fd3/5f14c9841516962a?lnk=gst&q=sujoy#5f14c9841516962a](https://groups.google.com/group/elasticsearch/browse_thread/thread/7c033ea3b9a92fd3/5f14c9841516962a?lnk=gst&q=sujoy#5f14c9841516962a)

I tweaked the discovery.zen.minimum\_master\_nodes parameter to get the  
some level of stability but I was then defying the whole concept of  
distributed cluster and failover.

Thanks a lot Shay for this fix

> <https://github.com/elastic/elasticsearch/issues/2042>

It gives me immense happiness and confidence when you so promptly  
address our concerns.

Thanks and Regards  
Jagdeep

---

<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, 3:22am UTC](https://discuss.elastic.co/t/network-resiliency-thumbs-up-shay/8197/2 "2017-07-06T03:22:54Z")

</div>