# Cluster / Configuration / Quorum **URL:** \ **Category:** Elasticsearch\ **Created:** [October 21, 2013, 3:42pm UTC](https://discuss.elastic.co/t/cluster-configuration-quorum/14042 "2013-10-21T15:42:48Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Nicolas\_Blanc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nicolas_blanc/32/2030_2.png) [@Nicolas\_Blanc](https://discuss.elastic.co/u/Nicolas_Blanc)\ **Post date:** [October 21, 2013, 3:42pm UTC](https://discuss.elastic.co/t/cluster-configuration-quorum/14042/1 "2013-10-21T15:42:48Z")
Hi all, My problem today is not so simple at all! I already have some big cluster in production. But, as of today my number of nodes is known and didn't change too much. Tomorrow i plan to be more and more elastic. I won't know the exact number of nodes at a given time, as it will depends on the load and some auto-scaling rules. All my platform is build with Chef, so i am able to determine the number of nodes with some tips. But i have a lot of questions: When i add a new master node, the minimum\_master\_nodes value is re-calculated accordingly... Is this value propagated to the whole cluster when the new master node come up ? Chef adapt the configuration of all es nodes, but don't restart them when already running. Do i need to change this value via a call to the API ([http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-update-settings.html](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-update-settings.html)) ? When i remove a node, i think i have no choice but calling the API to reduce the minimum\_master\_nodes, am i right ? Another question i have, is it a good idea to use unicast and defining all master nodes in conf files, or do i need to define just multicast ? And finally, i want to have a cluster between 2 zones, one is my actuel DC, and the other one if an ec2 vpc... What's the best way to interface the 2 zones ? Unicast + Multicast and EC2 + unicast ? Do i need to list each master node of the whole cluster in each conf files ? Thanks in advance to the one who will try to answer me. -- Nicolas Blanc. -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [October 21, 2013, 8:59pm UTC](https://discuss.elastic.co/t/cluster-configuration-quorum/14042/2 "2013-10-21T20:59:18Z")
Hey Nicolas, What I would probably do in your case is to split node roles: 3 nodes with data: false, master: true X data nodes: data: true, master: false Note that master nodes does not require "big machines". 512 Mb RAM, spinning disks, 1 core... No need to worry then about that setting. Just set it to 2. What do you think? About having 2 data centers, I would not recommend to connect directly your internal nodes with amazon unless you know that you have a very low latency Network. I would setup 2 clusters and would push docs from service layer to both clusters. HTH -- David 😉 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 21 oct. 2013 à 17:42, Nicolas Blanc [nicolas.blanc@blablacar.com](mailto:nicolas.blanc@blablacar.com) a écrit : Hi all, My problem today is not so simple at all! I already have some big cluster in production. But, as of today my number of nodes is known and didn't change too much. Tomorrow i plan to be more and more elastic. I won't know the exact number of nodes at a given time, as it will depends on the load and some auto-scaling rules. All my platform is build with Chef, so i am able to determine the number of nodes with some tips. But i have a lot of questions: When i add a new master node, the minimum\_master\_nodes value is re-calculated accordingly... Is this value propagated to the whole cluster when the new master node come up ? Chef adapt the configuration of all es nodes, but don't restart them when already running. Do i need to change this value via a call to the API ([http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-update-settings.html](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-update-settings.html)) ? When i remove a node, i think i have no choice but calling the API to reduce the minimum\_master\_nodes, am i right ? Another question i have, is it a good idea to use unicast and defining all master nodes in conf files, or do i need to define just multicast ? And finally, i want to have a cluster between 2 zones, one is my actuel DC, and the other one if an ec2 vpc... What's the best way to interface the 2 zones ? Unicast + Multicast and EC2 + unicast ? Do i need to list each master node of the whole cluster in each conf files ? Thanks in advance to the one who will try to answer me. -- Nicolas Blanc. -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Amit\_Soni](https://avatars.discourse-cdn.com/v4/letter/a/c0e974/32.png) [@Amit\_Soni](https://discuss.elastic.co/u/Amit_Soni)\ **Post date:** [October 22, 2013, 2:30am UTC](https://discuss.elastic.co/t/cluster-configuration-quorum/14042/3 "2013-10-22T02:30:05Z")
And if I correctly remember, in version 1.0, there is a provision to take snapshot which can solve for disaster recovery. _David_ - Just wondering if you have plans to support mechanism which would enable data replication across two data centers (more like near real time mirroring feature? -Amit. On Mon, Oct 21, 2013 at 1:59 PM, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote: > Hey Nicolas, > > What I would probably do in your case is to split node roles: > > 3 nodes with data: false, master: true > X data nodes: data: true, master: false > > Note that master nodes does not require "big machines". 512 Mb RAM, > spinning disks, 1 core... > > No need to worry then about that setting. Just set it to 2. > > What do you think? > > About having 2 data centers, I would not recommend to connect directly > your internal nodes with amazon unless you know that you have a very low > latency Network. > I would setup 2 clusters and would push docs from service layer to both > clusters. > > HTH > > -- > David 😉 > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > Le 21 oct. 2013 à 17:42, Nicolas Blanc [nicolas.blanc@blablacar.com](mailto:nicolas.blanc@blablacar.com) a > écrit : > > Hi all, > > My problem today is not so simple at all! I already have some big cluster > in production. But, as of today my number of nodes is known and didn't > change too much. Tomorrow i plan to be more and more elastic. I won't know > the exact number of nodes at a given time, as it will depends on the load > and some auto-scaling rules. > > All my platform is build with Chef, so i am able to determine the number > of nodes with some tips. But i have a lot of questions: > > When i add a new master node, the minimum\_master\_nodes value is > re-calculated accordingly... Is this value propagated to the whole cluster > when the new master node come up ? Chef adapt the configuration of all es > nodes, but don't restart them when already running. Do i need to change > this value via a call to the API ( > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-update-settings.html)) > ? When i remove a node, i think i have no choice but calling the API to > reduce the minimum\_master\_nodes, am i right ? > > Another question i have, is it a good idea to use unicast and defining all > master nodes in conf files, or do i need to define just multicast ? > > And finally, i want to have a cluster between 2 zones, one is my actuel > DC, and the other one if an ec2 vpc... What's the best way to interface the > 2 zones ? Unicast + Multicast and EC2 + unicast ? Do i need to list each > master node of the whole cluster in each conf files ? > > Thanks in advance to the one who will try to answer me. > > -- > Nicolas Blanc. > > -- > 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). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > -- > 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). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [October 22, 2013, 5:44am UTC](https://discuss.elastic.co/t/cluster-configuration-quorum/14042/4 "2013-10-22T05:44:53Z")
Yes but not in the short term. -- David 😉 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 22 oct. 2013 à 04:30, Amit Soni [amitsoni29@gmail.com](mailto:amitsoni29@gmail.com) a écrit : And if I correctly remember, in version 1.0, there is a provision to take snapshot which can solve for disaster recovery. David - Just wondering if you have plans to support mechanism which would enable data replication across two data centers (more like near real time mirroring feature? -Amit. > On Mon, Oct 21, 2013 at 1:59 PM, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote: > Hey Nicolas, > > What I would probably do in your case is to split node roles: > > 3 nodes with data: false, master: true > X data nodes: data: true, master: false > > Note that master nodes does not require "big machines". 512 Mb RAM, spinning disks, 1 core... > > No need to worry then about that setting. Just set it to 2. > > What do you think? > > About having 2 data centers, I would not recommend to connect directly your internal nodes with amazon unless you know that you have a very low latency Network. > I would setup 2 clusters and would push docs from service layer to both clusters. > > HTH > > -- > David 😉 > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > Le 21 oct. 2013 à 17:42, Nicolas Blanc [nicolas.blanc@blablacar.com](mailto:nicolas.blanc@blablacar.com) a écrit : > > Hi all, > > My problem today is not so simple at all! I already have some big cluster in production. But, as of today my number of nodes is known and didn't change too much. Tomorrow i plan to be more and more elastic. I won't know the exact number of nodes at a given time, as it will depends on the load and some auto-scaling rules. > > All my platform is build with Chef, so i am able to determine the number of nodes with some tips. But i have a lot of questions: > > When i add a new master node, the minimum\_master\_nodes value is re-calculated accordingly... Is this value propagated to the whole cluster when the new master node come up ? Chef adapt the configuration of all es nodes, but don't restart them when already running. Do i need to change this value via a call to the API ([Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-update-settings.html)) ? When i remove a node, i think i have no choice but calling the API to reduce the minimum\_master\_nodes, am i right ? > > Another question i have, is it a good idea to use unicast and defining all master nodes in conf files, or do i need to define just multicast ? > > And finally, i want to have a cluster between 2 zones, one is my actuel DC, and the other one if an ec2 vpc... What's the best way to interface the 2 zones ? Unicast + Multicast and EC2 + unicast ? Do i need to list each master node of the whole cluster in each conf files ? > > Thanks in advance to the one who will try to answer me. > > -- > Nicolas Blanc. > > ## -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > 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). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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, 2:11am UTC](https://discuss.elastic.co/t/cluster-configuration-quorum/14042/5 "2017-07-06T02:11:17Z")