# Adding the second node to one of the existing cluster's servers

**URL:** <https://discuss.elastic.co/t/adding-the-second-node-to-one-of-the-existing-clusters-servers/191423>\
**Category:** Elasticsearch\
**Created:** [July 19, 2019, 3:29pm UTC](https://discuss.elastic.co/t/adding-the-second-node-to-one-of-the-existing-clusters-servers/191423 "2019-07-19T15:29:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![metlovich97](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/metlovich97/32/43083_2.png) [@metlovich97](https://discuss.elastic.co/u/metlovich97)\
**Post date:** [July 19, 2019, 3:29pm UTC](https://discuss.elastic.co/t/adding-the-second-node-to-one-of-the-existing-clusters-servers/191423/1 "2019-07-19T15:29:50Z")

</div>

HI! We have a three node cluster on three servers. According to this [article](https://www.elastic.co/guide/en/elasticsearch/guide/current/heap-sizing.html) we can benefit from running the second node on one of our machines:

> Are you doing a lot of sorting/aggregations on analyzed strings (e.g. for word-tags, or SigTerms, etc)? Unfortunately that means you’ll need fielddata, which means you need heap space. Instead of one node with more than 512 GB of RAM, consider running two or more nodes on a single machine.

Is it possible to have this architecture (4 nodes on 3 servers)?

---

<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:** [August 16, 2019, 3:29pm UTC](https://discuss.elastic.co/t/adding-the-second-node-to-one-of-the-existing-clusters-servers/191423/2 "2019-08-16T15:29:52Z")

</div>

Closed on August 16, 2019, 3:29pm UTC

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