# 3 nodes configuration for efficiency

**URL:** <https://discuss.elastic.co/t/3-nodes-configuration-for-efficiency/82263>\
**Category:** Elasticsearch\
**Created:** [April 13, 2017, 9:25am UTC](https://discuss.elastic.co/t/3-nodes-configuration-for-efficiency/82263 "2017-04-13T09:25:01Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mahesh\_cs](https://avatars.discourse-cdn.com/v4/letter/m/71c47a/32.png) [@mahesh\_cs](https://discuss.elastic.co/u/mahesh_cs)\
**Post date:** [April 13, 2017, 9:25am UTC](https://discuss.elastic.co/t/3-nodes-configuration-for-efficiency/82263/1 "2017-04-13T09:25:01Z")

</div>

Hello,

I am fairly new to ELK stack. I have three servers and they have same processor and disk size, they only differ in size of RAM

server 1: 16 GB RAM  
server 2: 8 GB RAM  
server 3: 8 GB RAM

I read about various nodes in an articles and decide following architecture based on very little information.

server 1: elasticsearch (as it is taking more memory), data node, eligible master node, logstash, ingest

server 2: data node, eligible master node, logstash, ingest

sever 3: dedicated master node, kibana

I want to configure Kibana, logstash, elasticsearch on these sever so that it will give a result of query in minimum time. What is the best trade off or architecture suitable for this kind of specification and does the mentioned design make sense.

---

<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:** [April 13, 2017, 10:53am UTC](https://discuss.elastic.co/t/3-nodes-configuration-for-efficiency/82263/2 "2017-04-13T10:53:28Z")

</div>

I'd put elasticsearch alone to give it the maximum resources as possible.

Colocation of Kibana will only reduce the latency between elasticsearch and Kibana but I doubt that network is an issue those days or you have a very bad network you should fix 🙂

---

<div class="post-metadata">

**Author:** ![mahesh\_cs](https://avatars.discourse-cdn.com/v4/letter/m/71c47a/32.png) [@mahesh\_cs](https://discuss.elastic.co/u/mahesh_cs)\
**Post date:** [April 13, 2017, 10:59am UTC](https://discuss.elastic.co/t/3-nodes-configuration-for-efficiency/82263/3 "2017-04-13T10:59:16Z")

</div>

Thanks for your reply. Does it make sense if I configure like this

server 1: elasticsearch (as it is taking more memory), ingest

server 2: data node, eligible master node, logstash, ingest

sever 3: dedicated master node, kibana

---

<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:** [April 13, 2017, 11:34am UTC](https://discuss.elastic.co/t/3-nodes-configuration-for-efficiency/82263/4 "2017-04-13T11:34:32Z")

</div>

Yes. But I'd keep 1st node as master eligible to avoid split brain issues

---

<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:** [May 11, 2017, 11:34am UTC](https://discuss.elastic.co/t/3-nodes-configuration-for-efficiency/82263/5 "2017-05-11T11:34:57Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.