# Recommended discovery mechanism for production cluster on ec2

**URL:** <https://discuss.elastic.co/t/recommended-discovery-mechanism-for-production-cluster-on-ec2/20722>\
**Category:** Elasticsearch\
**Created:** [November 13, 2014, 12:25pm UTC](https://discuss.elastic.co/t/recommended-discovery-mechanism-for-production-cluster-on-ec2/20722 "2014-11-13T12:25:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Itai\_Frenkel](https://avatars.discourse-cdn.com/v4/letter/i/ecc23a/32.png) [@Itai\_Frenkel](https://discuss.elastic.co/u/Itai_Frenkel)\
**Post date:** [November 13, 2014, 12:25pm UTC](https://discuss.elastic.co/t/recommended-discovery-mechanism-for-production-cluster-on-ec2/20722/1 "2014-11-13T12:25:32Z")

</div>

Hi,

What is the recommended discovery mechanism for production clusters on ec2?

Zen: My main concerns is the possibility of dedicated master nodes changing  
their ip addresses (could happen on ec2). Does zen uses the configured  
unicast hosts just as gossip seed, or is it a static list? If it is just a  
gossip seed, does zen persist the gossip back to disk in case a process  
restart is needed and the original ip addresses are out of date? If it does  
not persist gossiped ip address to disk, do I need a script that injects  
fresh seeds each time elasticsearch service starts?

ec2: My main concern is the resiliency of the cluster if ec2 api returns  
inconsistent results causing some kind of split brain scenario. Has such a  
thing been reported?

zookeeper: This plugin has been reported to work better than zen discovery  
regarding to split brain. Is this observation still relevant in v1.4? I am  
willing to risk an unofficial plugin if it makes the cluster more stable.

Regards,  
Itai

--  
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/09e144c4-41b7-44a1-b18b-2bee07aae71d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/09e144c4-41b7-44a1-b18b-2bee07aae71d%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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, 12:50am UTC](https://discuss.elastic.co/t/recommended-discovery-mechanism-for-production-cluster-on-ec2/20722/2 "2017-07-06T00:50:17Z")

</div>