# Es architechture

**URL:** <https://discuss.elastic.co/t/es-architechture/14441>\
**Category:** Elasticsearch\
**Created:** [November 17, 2013, 10:29pm UTC](https://discuss.elastic.co/t/es-architechture/14441 "2013-11-17T22:29:53Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![danielr](https://avatars.discourse-cdn.com/v4/letter/d/f17d59/32.png) [@danielr](https://discuss.elastic.co/u/danielr)\
**Post date:** [November 17, 2013, 10:29pm UTC](https://discuss.elastic.co/t/es-architechture/14441/1 "2013-11-17T22:29:53Z")

</div>

Hi! I want to use es as my resources server.  
To support my users, I was planning on raising 2 servers with one instance  
on each server.  
Configuring the two nodes as a cluster with 8 shards for future scaling and  
2 replicas for better performance .  
Also i want to set zen discovery to use unicast so that the two nodes will  
work synchronically.

My question is, _will this configuration work for me?_  
How do i make sure that it works? Just by calling the indexes and check its  
data?

10X  
Daniel

--  
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).

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 18, 2013, 12:19am UTC](https://discuss.elastic.co/t/es-architechture/14441/2 "2013-11-18T00:19:54Z")

</div>

If you're looking to add another node in soon then keep that replica  
number, otherwise 1 replica will be enough (one per node). You can change  
the replica number at a later date if you wish.

That config will work for what you want. Install a plugin like  
kopf/elastichq/bigdesk and you will easily see what the status of the  
cluster is, some of them also allow you to view documents in an index.

Regards,  
Mark Walkom

Infrastructure Engineer  
Campaign Monitor  
email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com)  
web: [www.campaignmonitor.com](http://www.campaignmonitor.com)

On 18 November 2013 09:29, DanielR [danielrastaziv@gmail.com](mailto:danielrastaziv@gmail.com) wrote:

> Hi! I want to use es as my resources server.  
> To support my users, I was planning on raising 2 servers with one instance  
> on each server.  
> Configuring the two nodes as a cluster with 8 shards for future scaling and  
> 2 replicas for better performance .  
> Also i want to set zen discovery to use unicast so that the two nodes will  
> work synchronically.
> 
> My question is, _will this configuration work for me?_  
> How do i make sure that it works? Just by calling the indexes and check its  
> data?
> 
> 10X  
> Daniel
> 
> --  
> 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).

---

<div class="post-metadata">

**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:** [November 18, 2013, 2:14am UTC](https://discuss.elastic.co/t/es-architechture/14441/3 "2013-11-18T02:14:47Z")

</div>

In addition to this, for production, I would recommend to start with 3 nodes. It will help you to reduce split brain issues risk.  
Set minimum master node to 2.

My 2 cents.

--  
David 😉  
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 18 nov. 2013 à 01:19, Mark Walkom [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) a écrit :

If you're looking to add another node in soon then keep that replica number, otherwise 1 replica will be enough (one per node). You can change the replica number at a later date if you wish.

That config will work for what you want. Install a plugin like kopf/elastichq/bigdesk and you will easily see what the status of the cluster is, some of them also allow you to view documents in an index.

Regards,  
Mark Walkom

Infrastructure Engineer  
Campaign Monitor  
email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com)  
web: [www.campaignmonitor.com](http://www.campaignmonitor.com)

> On 18 November 2013 09:29, DanielR [danielrastaziv@gmail.com](mailto:danielrastaziv@gmail.com) wrote:  
> Hi! I want to use es as my resources server.  
> To support my users, I was planning on raising 2 servers with one instance  
> on each server.  
> Configuring the two nodes as a cluster with 8 shards for future scaling and  
> 2 replicas for better performance .  
> Also i want to set zen discovery to use unicast so that the two nodes will  
> work synchronically.
> 
> My question is, will this configuration work for me?  
> How do i make sure that it works? Just by calling the indexes and check its  
> data?
> 
> ## 10X Daniel
> 
> 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).

---

<div class="post-metadata">

**Author:** ![Alex\_Brasetvik\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_brasetvik_2/32/1994_2.png) [@Alex\_Brasetvik\_2](https://discuss.elastic.co/u/Alex_Brasetvik_2)\
**Post date:** [November 18, 2013, 1:33pm UTC](https://discuss.elastic.co/t/es-architechture/14441/4 "2013-11-18T13:33:25Z")

</div>

> In addition to this, for production, I would recommend to start with 3 nodes. It will help you to reduce split brain issues risk.  
> Set minimum master node to 2.

As David points out, you’ll really want to have minimum master nodes of 2, even though the cluster only has two nodes: In a two-node cluster, you need to have both nodes to have a majority. 1 of 2 is not a majority, but a split brain.

Thus the third node.

Note, however, that the third node can be a cheap node without any data. (I.e. `node.data` is false) Then it’ll just participate to form a majority if a network partition happens.

I’ve written an article that has a bit more details about this here: [Elasticsearch: The Official Distributed Search & Analytics Engine | Elastic](https://www.found.no/foundation/elasticsearch-in-production/#networking)

Hope this helps! 🙂

Best regards,

Alex Brasetvik

Found AS  
Hosted Elasticsearch – www.found.no

--  
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).

---

<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, 2:06am UTC](https://discuss.elastic.co/t/es-architechture/14441/5 "2017-07-06T02:06:26Z")

</div>


