# Announcement: ZooKeeper Discovery Plugin for Elasticsearch **URL:** \ **Category:** Elasticsearch\ **Created:** [July 11, 2012, 12:14am UTC](https://discuss.elastic.co/t/announcement-zookeeper-discovery-plugin-for-elasticsearch/8381 "2012-07-11T00:14:12Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Igor\_Motov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_motov/32/45193_2.png) [@Igor\_Motov](https://discuss.elastic.co/u/Igor_Motov)\ **Post date:** [July 11, 2012, 12:14am UTC](https://discuss.elastic.co/t/announcement-zookeeper-discovery-plugin-for-elasticsearch/8381/1 "2012-07-11T00:14:12Z")
Sonian, Inc. has released ZooKeeper Discovery Plugin as open source under Apache 2.0 License. The ZooKeeper plugin is a drop-in replacement for Zen Discovery. It uses Apache ZooKeeper for master election, node fault detection and state publishing. This plugin is still experimental and not recommended to be used in production environments. For more information visit plugin project page: > **[sonian/elasticsearch-zookeeper](https://github.com/sonian/elasticsearch-zookeeper)** > > Contribute to elasticsearch-zookeeper development by creating an account on GitHub. ---
**Author:** ![otisg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/otisg/32/492_2.png) [@otisg](https://discuss.elastic.co/u/otisg)\ **Post date:** [July 11, 2012, 4:39am UTC](https://discuss.elastic.co/t/announcement-zookeeper-discovery-plugin-for-elasticsearch/8381/2 "2012-07-11T04:39:30Z")
Very nice. When and/or why should one use this instead of Zen Discovery? What are pros/cons of one vs. the other? ## Thanks, Otis Search Analytics - [Cloud Monitoring Tools & Services | Sematext](http://sematext.com/search-analytics/index.html) Scalable Performance Monitoring - [Sematext Monitoring | Infrastructure Monitoring Service](http://sematext.com/spm/index.html) On Tuesday, July 10, 2012 8:14:12 PM UTC-4, Igor Motov wrote: > Sonian, Inc. has released ZooKeeper Discovery Plugin as open source under > Apache 2.0 License. The ZooKeeper plugin is a drop-in replacement for Zen > Discovery. It uses Apache ZooKeeper for master election, node fault > detection and state publishing. This plugin is still experimental and not > recommended to be used in production environments. > > For more information visit plugin project page: > [GitHub - sonian/elasticsearch-zookeeper](https://github.com/sonian/elasticsearch-zookeeper) ---
**Author:** ![Igor\_Motov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_motov/32/45193_2.png) [@Igor\_Motov](https://discuss.elastic.co/u/Igor_Motov)\ **Post date:** [July 11, 2012, 3:56pm UTC](https://discuss.elastic.co/t/announcement-zookeeper-discovery-plugin-for-elasticsearch/8381/3 "2012-07-11T15:56:48Z")
ZooKeeper Discovery can simplify setup and configuration in multicast-unfriendly, dynamically changing environments that are already using Apache ZooKeeper. ZooKeeper Discovery relies on ZooKeeper to keep track of nodes in the cluster and perform master election, providing consistent view of the cluster and identify of the master node. On the other side, it's not as field tested as Zen Discovery is, so it safe to assume that it still has some issues to discover and fix. Igor On Wednesday, July 11, 2012 12:39:30 AM UTC-4, Otis Gospodnetic wrote: > Very nice. > > When and/or why should one use this instead of Zen Discovery? What are > pros/cons of one vs. the other? > > ## Thanks, Otis > > Search Analytics - [Cloud Monitoring Tools & Services | Sematext](http://sematext.com/search-analytics/index.html) > Scalable Performance Monitoring - [Sematext Monitoring | Infrastructure Monitoring Service](http://sematext.com/spm/index.html) > > On Tuesday, July 10, 2012 8:14:12 PM UTC-4, Igor Motov wrote: > > > Sonian, Inc. has released ZooKeeper Discovery Plugin as open source under > > Apache 2.0 License. The ZooKeeper plugin is a drop-in replacement for Zen > > Discovery. It uses Apache ZooKeeper for master election, node fault > > detection and state publishing. This plugin is still experimental and not > > recommended to be used in production environments. > > > > For more information visit plugin project page: > > [GitHub - sonian/elasticsearch-zookeeper](https://github.com/sonian/elasticsearch-zookeeper) ---
**Author:** ![otisg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/otisg/32/492_2.png) [@otisg](https://discuss.elastic.co/u/otisg)\ **Post date:** [July 12, 2012, 2:59am UTC](https://discuss.elastic.co/t/announcement-zookeeper-discovery-plugin-for-elasticsearch/8381/4 "2012-07-12T02:59:31Z")
Thanks Igor. You should stick that in the README. Also, does using that make any difference when it comes to split brain? See: 1. [https://groups.google.com/d/msg/elasticsearch/\_QWKLnpvmeU/csbvkqaFF\_0J](https://groups.google.com/d/msg/elasticsearch/_QWKLnpvmeU/csbvkqaFF_0J) 2. [http://search-lucene.com/m/aN5vk1xuETB1](http://search-lucene.com/m/aN5vk1xuETB1) ## Otis Search Analytics - [Cloud Monitoring Tools & Services | Sematext](http://sematext.com/search-analytics/index.html) Scalable Performance Monitoring - [Sematext Monitoring | Infrastructure Monitoring Service](http://sematext.com/spm/index.html) On Wednesday, July 11, 2012 11:56:48 AM UTC-4, Igor Motov wrote: > ZooKeeper Discovery can simplify setup and configuration in > multicast-unfriendly, dynamically changing environments that are already > using Apache ZooKeeper. ZooKeeper Discovery relies on ZooKeeper to keep > track of nodes in the cluster and perform master election, providing > consistent view of the cluster and identify of the master node. On the > other side, it's not as field tested as Zen Discovery is, so it safe to > assume that it still has some issues to discover and fix. > > Igor > > On Wednesday, July 11, 2012 12:39:30 AM UTC-4, Otis Gospodnetic wrote: > > > Very nice. > > > > When and/or why should one use this instead of Zen Discovery? What are > > pros/cons of one vs. the other? > > > > ## Thanks, Otis > > > > Search Analytics - [Cloud Monitoring Tools & Services | Sematext](http://sematext.com/search-analytics/index.html) > > Scalable Performance Monitoring - [Sematext Monitoring | Infrastructure Monitoring Service](http://sematext.com/spm/index.html) > > > > On Tuesday, July 10, 2012 8:14:12 PM UTC-4, Igor Motov wrote: > > > > > Sonian, Inc. has released ZooKeeper Discovery Plugin as open source > > > under Apache 2.0 License. The ZooKeeper plugin is a drop-in replacement for > > > Zen Discovery. It uses Apache ZooKeeper for master election, node fault > > > detection and state publishing. This plugin is still experimental and not > > > recommended to be used in production environments. > > > > > > For more information visit plugin project page: > > > [GitHub - sonian/elasticsearch-zookeeper](https://github.com/sonian/elasticsearch-zookeeper) ---
**Author:** ![Igor\_Motov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_motov/32/45193_2.png) [@Igor\_Motov](https://discuss.elastic.co/u/Igor_Motov)\ **Post date:** [July 12, 2012, 3:38pm UTC](https://discuss.elastic.co/t/announcement-zookeeper-discovery-plugin-for-elasticsearch/8381/5 "2012-07-12T15:38:49Z")
Avoiding split brain was one of the original driving forces behind ZooKeeper Discovery plugin development. Since then elasticsearch split brain resistance was significantly improved. Indeed, properly specified discovery.zen.minimum\_master\_nodes helps clusters to remain coherent. In case of ZooKeeper Discovery plugin, quorum is maintained by ZooKeeper nodes, so it's not necessary to specify discovery.zen.minimum\_master\_nodes on each elasticsearch node. Igor On Wednesday, July 11, 2012 10:59:31 PM UTC-4, Otis Gospodnetic wrote: > Thanks Igor. You should stick that in the README. > > Also, does using that make any difference when it comes to split brain? > > See: > > 1. [https://groups.google.com/d/msg/elasticsearch/\_QWKLnpvmeU/csbvkqaFF\_0J](https://groups.google.com/d/msg/elasticsearch/_QWKLnpvmeU/csbvkqaFF_0J) > 2. [http://search-lucene.com/m/aN5vk1xuETB1](http://search-lucene.com/m/aN5vk1xuETB1) > > ## Otis > > Search Analytics - [Cloud Monitoring Tools & Services | Sematext](http://sematext.com/search-analytics/index.html) > Scalable Performance Monitoring - [Sematext Monitoring | Infrastructure Monitoring Service](http://sematext.com/spm/index.html) > > On Wednesday, July 11, 2012 11:56:48 AM UTC-4, Igor Motov wrote: > > > ZooKeeper Discovery can simplify setup and configuration in > > multicast-unfriendly, dynamically changing environments that are already > > using Apache ZooKeeper. ZooKeeper Discovery relies on ZooKeeper to keep > > track of nodes in the cluster and perform master election, providing > > consistent view of the cluster and identify of the master node. On the > > other side, it's not as field tested as Zen Discovery is, so it safe to > > assume that it still has some issues to discover and fix. > > > > Igor > > > > On Wednesday, July 11, 2012 12:39:30 AM UTC-4, Otis Gospodnetic wrote: > > > > > Very nice. > > > > > > When and/or why should one use this instead of Zen Discovery? What are > > > pros/cons of one vs. the other? > > > > > > ## Thanks, Otis > > > > > > Search Analytics - [Cloud Monitoring Tools & Services | Sematext](http://sematext.com/search-analytics/index.html) > > > Scalable Performance Monitoring - [Sematext Monitoring | Infrastructure Monitoring Service](http://sematext.com/spm/index.html) > > > > > > On Tuesday, July 10, 2012 8:14:12 PM UTC-4, Igor Motov wrote: > > > > > > > Sonian, Inc. has released ZooKeeper Discovery Plugin as open source > > > > under Apache 2.0 License. The ZooKeeper plugin is a drop-in replacement for > > > > Zen Discovery. It uses Apache ZooKeeper for master election, node fault > > > > detection and state publishing. This plugin is still experimental and not > > > > recommended to be used in production environments. > > > > > > > > For more information visit plugin project page: > > > > [GitHub - sonian/elasticsearch-zookeeper](https://github.com/sonian/elasticsearch-zookeeper) ---
**Author:** ![otisg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/otisg/32/492_2.png) [@otisg](https://discuss.elastic.co/u/otisg)\ **Post date:** [July 23, 2012, 12:02am UTC](https://discuss.elastic.co/t/announcement-zookeeper-discovery-plugin-for-elasticsearch/8381/6 "2012-07-23T00:02:28Z")
Hi Igor, Does this mean that the ZK Discovery plugin's _only_ advantage is in multicast-unfriendly environments? (and I don't mean this in a bad way at all!) If so, are you planning on some other functionality that would increase the difference between Zen and ZK Discovery plugin? ## Thanks, Otis Search Analytics - [Cloud Monitoring Tools & Services | Sematext](http://sematext.com/search-analytics/index.html) Scalable Performance Monitoring - [Sematext Monitoring | Infrastructure Monitoring Service](http://sematext.com/spm/index.html) On Thursday, July 12, 2012 11:38:49 AM UTC-4, Igor Motov wrote: > Avoiding split brain was one of the original driving forces behind > ZooKeeper Discovery plugin development. Since then elasticsearch split > brain resistance was significantly improved. Indeed, properly > specified discovery.zen.minimum\_master\_nodes helps clusters to remain > coherent. In case of ZooKeeper Discovery plugin, quorum is maintained by > ZooKeeper nodes, so it's not necessary to specify > discovery.zen.minimum\_master\_nodes on each elasticsearch node. > > Igor > > On Wednesday, July 11, 2012 10:59:31 PM UTC-4, Otis Gospodnetic wrote: > > > Thanks Igor. You should stick that in the README. > > > > Also, does using that make any difference when it comes to split brain? > > > > See: > > > > 1. [https://groups.google.com/d/msg/elasticsearch/\_QWKLnpvmeU/csbvkqaFF\_0J](https://groups.google.com/d/msg/elasticsearch/_QWKLnpvmeU/csbvkqaFF_0J) > > 2. [http://search-lucene.com/m/aN5vk1xuETB1](http://search-lucene.com/m/aN5vk1xuETB1) > > > > ## Otis > > > > Search Analytics - [Cloud Monitoring Tools & Services | Sematext](http://sematext.com/search-analytics/index.html) > > Scalable Performance Monitoring - [Sematext Monitoring | Infrastructure Monitoring Service](http://sematext.com/spm/index.html) > > > > On Wednesday, July 11, 2012 11:56:48 AM UTC-4, Igor Motov wrote: > > > > > ZooKeeper Discovery can simplify setup and configuration in > > > multicast-unfriendly, dynamically changing environments that are already > > > using Apache ZooKeeper. ZooKeeper Discovery relies on ZooKeeper to keep > > > track of nodes in the cluster and perform master election, providing > > > consistent view of the cluster and identify of the master node. On the > > > other side, it's not as field tested as Zen Discovery is, so it safe to > > > assume that it still has some issues to discover and fix. > > > > > > Igor > > > > > > On Wednesday, July 11, 2012 12:39:30 AM UTC-4, Otis Gospodnetic wrote: > > > > > > > Very nice. > > > > > > > > When and/or why should one use this instead of Zen Discovery? What are > > > > pros/cons of one vs. the other? > > > > > > > > ## Thanks, Otis > > > > > > > > Search Analytics - [Cloud Monitoring Tools & Services | Sematext](http://sematext.com/search-analytics/index.html) > > > > Scalable Performance Monitoring - [Sematext Monitoring | Infrastructure Monitoring Service](http://sematext.com/spm/index.html) > > > > > > > > On Tuesday, July 10, 2012 8:14:12 PM UTC-4, Igor Motov wrote: > > > > > > > > > Sonian, Inc. has released ZooKeeper Discovery Plugin as open source > > > > > under Apache 2.0 License. The ZooKeeper plugin is a drop-in replacement for > > > > > Zen Discovery. It uses Apache ZooKeeper for master election, node fault > > > > > detection and state publishing. This plugin is still experimental and not > > > > > recommended to be used in production environments. > > > > > > > > > > For more information visit plugin project page: > > > > > [GitHub - sonian/elasticsearch-zookeeper](https://github.com/sonian/elasticsearch-zookeeper) ---
**Author:** ![Igor\_Motov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_motov/32/45193_2.png) [@Igor\_Motov](https://discuss.elastic.co/u/Igor_Motov)\ **Post date:** [July 24, 2012, 2:12pm UTC](https://discuss.elastic.co/t/announcement-zookeeper-discovery-plugin-for-elasticsearch/8381/7 "2012-07-24T14:12:01Z")
Hi Otis, I think I could agree with your statement. ZK Discovery helps avoiding split-brain in dynamically changing clusters running in multicast-unfriendly environments without the need to change config files on servers. There are some things that I would like to improve internally, but feature-wise it satisfies all our needs at the moment and we don't have any immediate plans to add any new functionality. Igor On Sunday, July 22, 2012 8:02:28 PM UTC-4, Otis Gospodnetic wrote: > Hi Igor, > > Does this mean that the ZK Discovery plugin's _only_ advantage is in > multicast-unfriendly environments? (and I don't mean this in a bad way at > all!) If so, are you planning on some other functionality that would > increase the difference between Zen and ZK Discovery plugin? > > ## Thanks, Otis > > Search Analytics - [Cloud Monitoring Tools & Services | Sematext](http://sematext.com/search-analytics/index.html) > Scalable Performance Monitoring - [Sematext Monitoring | Infrastructure Monitoring Service](http://sematext.com/spm/index.html) > > On Thursday, July 12, 2012 11:38:49 AM UTC-4, Igor Motov wrote: > > > Avoiding split brain was one of the original driving forces behind > > ZooKeeper Discovery plugin development. Since then elasticsearch split > > brain resistance was significantly improved. Indeed, properly > > specified discovery.zen.minimum\_master\_nodes helps clusters to remain > > coherent. In case of ZooKeeper Discovery plugin, quorum is maintained by > > ZooKeeper nodes, so it's not necessary to specify > > discovery.zen.minimum\_master\_nodes on each elasticsearch node. > > > > Igor > > > > On Wednesday, July 11, 2012 10:59:31 PM UTC-4, Otis Gospodnetic wrote: > > > > > Thanks Igor. You should stick that in the README. > > > > > > Also, does using that make any difference when it comes to split brain? > > > > > > See: > > > 1) > > > [https://groups.google.com/d/msg/elasticsearch/\_QWKLnpvmeU/csbvkqaFF\_0J](https://groups.google.com/d/msg/elasticsearch/_QWKLnpvmeU/csbvkqaFF_0J) > > > 2) [http://search-lucene.com/m/aN5vk1xuETB1](http://search-lucene.com/m/aN5vk1xuETB1) > > > > > > ## Otis > > > > > > Search Analytics - [Cloud Monitoring Tools & Services | Sematext](http://sematext.com/search-analytics/index.html) > > > Scalable Performance Monitoring - [Sematext Monitoring | Infrastructure Monitoring Service](http://sematext.com/spm/index.html) > > > > > > On Wednesday, July 11, 2012 11:56:48 AM UTC-4, Igor Motov wrote: > > > > > > > ZooKeeper Discovery can simplify setup and configuration in > > > > multicast-unfriendly, dynamically changing environments that are already > > > > using Apache ZooKeeper. ZooKeeper Discovery relies on ZooKeeper to keep > > > > track of nodes in the cluster and perform master election, providing > > > > consistent view of the cluster and identify of the master node. On the > > > > other side, it's not as field tested as Zen Discovery is, so it safe to > > > > assume that it still has some issues to discover and fix. > > > > > > > > Igor > > > > > > > > On Wednesday, July 11, 2012 12:39:30 AM UTC-4, Otis Gospodnetic wrote: > > > > > > > > > Very nice. > > > > > > > > > > When and/or why should one use this instead of Zen Discovery? What > > > > > are pros/cons of one vs. the other? > > > > > > > > > > ## Thanks, Otis > > > > > > > > > > Search Analytics - [Cloud Monitoring Tools & Services | Sematext](http://sematext.com/search-analytics/index.html) > > > > > Scalable Performance Monitoring - [Sematext Monitoring | Infrastructure Monitoring Service](http://sematext.com/spm/index.html) > > > > > > > > > > On Tuesday, July 10, 2012 8:14:12 PM UTC-4, Igor Motov wrote: > > > > > > > > > > > Sonian, Inc. has released ZooKeeper Discovery Plugin as open source > > > > > > under Apache 2.0 License. The ZooKeeper plugin is a drop-in replacement for > > > > > > Zen Discovery. It uses Apache ZooKeeper for master election, node fault > > > > > > detection and state publishing. This plugin is still experimental and not > > > > > > recommended to be used in production environments. > > > > > > > > > > > > For more information visit plugin project page: > > > > > > [GitHub - sonian/elasticsearch-zookeeper](https://github.com/sonian/elasticsearch-zookeeper) ---
**Author:** ![Matt\_Wise](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/matt_wise/32/701_2.png) [@Matt\_Wise](https://discuss.elastic.co/u/Matt_Wise)\ **Post date:** [November 7, 2012, 5:55pm UTC](https://discuss.elastic.co/t/announcement-zookeeper-discovery-plugin-for-elasticsearch/8381/8 "2012-11-07T17:55:59Z")
Just wanted to say Thanks for developing this. We were using our own in-house scripts to coordinate Elasticsearch with ZooKeeper, but your plugin is excellent. It works very well, and is extremely simple to setup. I hope you keep developing it for future versions of ZooKeeper. --Matt [Nextdoor.com](http://Nextdoor.com), Inc. On Tuesday, July 10, 2012 5:14:12 PM UTC-7, Igor Motov wrote: > Sonian, Inc. has released ZooKeeper Discovery Plugin as open source under > Apache 2.0 License. The ZooKeeper plugin is a drop-in replacement for Zen > Discovery. It uses Apache ZooKeeper for master election, node fault > detection and state publishing. This plugin is still experimental and not > recommended to be used in production environments. > > For more information visit plugin project page: > [GitHub - sonian/elasticsearch-zookeeper](https://github.com/sonian/elasticsearch-zookeeper) -- ---
**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:05am UTC](https://discuss.elastic.co/t/announcement-zookeeper-discovery-plugin-for-elasticsearch/8381/9 "2017-07-06T03:05:39Z")