# 2 Node Cluster, 1 node being passive **URL:** \ **Category:** Elasticsearch\ **Created:** [June 25, 2013, 1:09am UTC](https://discuss.elastic.co/t/2-node-cluster-1-node-being-passive/12533 "2013-06-25T01:09:04Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![David\_Charle](https://avatars.discourse-cdn.com/v4/letter/d/f08c70/32.png) [@David\_Charle](https://discuss.elastic.co/u/David_Charle)\ **Post date:** [June 25, 2013, 1:09am UTC](https://discuss.elastic.co/t/2-node-cluster-1-node-being-passive/12533/1 "2013-06-25T01:09:04Z")
Hi I am newbie to ES, and wanted to get simple 2 node cluster (1 in one DC and another one in another DC) .. think as simple master-\>slave; where one being the primary for all activities; and another being just a slave with up2date indexes and can be used for failover without waiting on rebuilding the indexes. Basically don't want secondary node to participate in live requests due to latency it introduces. Any recommendations on best configuration ? My proposal: _Node A (master)_ node.master: true node.data: true index.number\_of\_shards: 5 # need this for speeding up index time index.number\_of\_replicas: 1 _Node B (slave)_ node.master: false node.data: true index.number\_of\_shards: 5 index.number\_of\_replicas: 1 Does this work ? Thanks David -- 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:** ![radu\_gheorghe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/radu_gheorghe/32/556_2.png) [@radu\_gheorghe](https://discuss.elastic.co/u/radu_gheorghe)\ **Post date:** [June 25, 2013, 6:41am UTC](https://discuss.elastic.co/t/2-node-cluster-1-node-being-passive/12533/2 "2013-06-25T06:41:40Z")
Hi David, I think the master can be either node, because it doesn't do much work anyway. What you're probably interested in is which node is loaded with indexing and search requests. Indexing requests will hit both anyway, because you need both nodes to be in sync. So you're left with searching, where you should be able to use search preference to specify which node would be hit by searches if it's up (\_prefer\_node:xyz): > **[Elastic — The Search AI Company](https://www.elastic.co)** > > Power insights and outcomes with The Elastic Search AI Platform. See into your data and find answers that matter with enterprise solutions designed to help you accelerate time to insight. Try Elastic ... ## Best regards, Radu [http://sematext.com/](http://sematext.com/) -- Elasticsearch -- Solr -- Lucene On Tue, Jun 25, 2013 at 4:09 AM, David Charle [dbchar2012@gmail.com](mailto:dbchar2012@gmail.com) wrote: > Hi > > I am newbie to ES, and wanted to get simple 2 node cluster (1 in one DC > and another one in another DC) .. think as simple master-\>slave; where one > being the primary for all activities; and another being just a slave with > up2date indexes and can be used for failover without waiting on rebuilding > the indexes. Basically don't want secondary node to participate in live > requests due to latency it introduces. > > Any recommendations on best configuration ? > > My proposal: > > _Node A (master)_ > node.master: true > node.data: true > index.number\_of\_shards: 5 # need this for speeding up index time > index.number\_of\_replicas: 1 > > _Node B (slave)_ > node.master: false > node.data: true > index.number\_of\_shards: 5 > index.number\_of\_replicas: 1 > > Does this work ? > > Thanks > David > > -- > 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:** ![alap](https://avatars.discourse-cdn.com/v4/letter/a/67e7ee/32.png) [@alap](https://discuss.elastic.co/u/alap)\ **Post date:** [November 13, 2013, 11:37pm UTC](https://discuss.elastic.co/t/2-node-cluster-1-node-being-passive/12533/3 "2013-11-13T23:37:36Z")
hi, and why you don't use this configuration Any recommendations on best configuration ? My proposal: Node A (master) node.master: true node.data: true index.number\_of\_shards: 5 # need this for speeding up index time index.number\_of\_replicas: 1 Node B (slave) node.master: true node.data: true index.number\_of\_shards: 5 index.number\_of\_replicas: 1 whith a physical loadbalancer for load is two node. if the node A is down the node 2 logs. and after the node 1 is UP we have all data any times for me. ---
**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:07am UTC](https://discuss.elastic.co/t/2-node-cluster-1-node-being-passive/12533/4 "2017-07-06T02:07:21Z")