# 3 nodes(7.17) on a single server

**URL:** <https://discuss.elastic.co/t/3-nodes-7-17-on-a-single-server/359410>\
**Category:** Elasticsearch\
**Created:** [May 13, 2024, 7:23pm UTC](https://discuss.elastic.co/t/3-nodes-7-17-on-a-single-server/359410 "2024-05-13T19:23:38Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![bfarr11](https://avatars.discourse-cdn.com/v4/letter/b/77aa72/32.png) [@bfarr11](https://discuss.elastic.co/u/bfarr11)\
**Post date:** [May 13, 2024, 7:23pm UTC](https://discuss.elastic.co/t/3-nodes-7-17-on-a-single-server/359410/1 "2024-05-13T19:23:38Z")

</div>

I need help with the configuration to run 3 nodes on a single server. It has 32 core, 128GB RAM, 10T disk - so plenty of space.

Please do not post with negative - you should not do this posts. I simply need help with the configurations to get this to work.

---

<div class="post-metadata">

**Author:** ![bfarr11](https://avatars.discourse-cdn.com/v4/letter/b/77aa72/32.png) [@bfarr11](https://discuss.elastic.co/u/bfarr11)\
**Post date:** [May 13, 2024, 8:26pm UTC](https://discuss.elastic.co/t/3-nodes-7-17-on-a-single-server/359410/2 "2024-05-13T20:26:52Z")

</div>

Apologize. I forgot OS info. It is RHEL8.

---

<div class="post-metadata">

**Author:** ![yago82](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yago82/32/97755_2.png) [@yago82](https://discuss.elastic.co/u/yago82)\
**Post date:** [May 14, 2024, 10:13am UTC](https://discuss.elastic.co/t/3-nodes-7-17-on-a-single-server/359410/3 "2024-05-14T10:13:02Z")

</div>

> [@bfarr11](#):
>
> I need help with the configuration to run 3 nodes on a single server. It has 32 core, 128GB RAM, 10T disk - so plenty of space.
> 
> Please do not post with negative - you should not do this posts. I simply need help with the configurations to get this to work.

Hi,

using Docker can simplify the process of running multiple Elasticsearch nodes on a single server. Each Elasticsearch node can run in its own Docker container, with its own isolated environment and resources.

Regards

---

<div class="post-metadata">

**Author:** ![bfarr11](https://avatars.discourse-cdn.com/v4/letter/b/77aa72/32.png) [@bfarr11](https://discuss.elastic.co/u/bfarr11)\
**Post date:** [May 19, 2024, 12:12am UTC](https://discuss.elastic.co/t/3-nodes-7-17-on-a-single-server/359410/4 "2024-05-19T00:12:49Z")

</div>

Thank you but I don't want container or VMs. I need 3 nodes running on 1 machine.

I have tried all of the documentation around changed the ES\_PATH\_CONF to point to my new directory. I created a new service file and changed all of the configs to point to it. I also modified the elasticsearch-env file to make sure it reads the updted ES\_PATH\_CONF. It still doesn't start and throws out:

_ **Exception in thread "main" java.nio.file.NoSuchFileException: /etc/elasticsearch/elasticsearch.yml** _

There is somewhere not specified that is forcing it to look at default configuration file directory and I need help finding that.

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [May 19, 2024, 1:29am UTC](https://discuss.elastic.co/t/3-nodes-7-17-on-a-single-server/359410/5 "2024-05-19T01:29:36Z")

</div>

> [@bfarr11](#):
>
> I created a new service file and changed all of the configs to point to it. I also modified the elasticsearch-env file to make sure it reads the updted ES\_PATH\_CONF.

Please share the configurations you created.

> [@bfarr11](#):
>
> Exception in thread "main" java.nio.file.NoSuchFileException: /etc/elasticsearch/elasticsearch.yml

How you start it? You would need to create 3 custom systemd services files, you should not use the `elasticsearch` service installed by the `rpm` package.

Basically you will need

- one data path for each instance
- one log paht for each instance
- one configuration file for each instance
- one systemd service for each instance.

I would say that the best approach would be to have 3 installations, download elasticsearch using the `.tar.gz` file and unpack this file into 3 different paths, one for each instance.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [May 19, 2024, 2:35am UTC](https://discuss.elastic.co/t/3-nodes-7-17-on-a-single-server/359410/6 "2024-05-19T02:35:42Z")

</div>

> [@leandrojmp](#):
>
> I would say that the best approach would be to have 3 installations, download elasticsearch using the `.tar.gz` file and unpack this file into 3 different paths, one for each instance.

Absolutely!

---

<div class="post-metadata">

**Author:** ![bfarr11](https://avatars.discourse-cdn.com/v4/letter/b/77aa72/32.png) [@bfarr11](https://discuss.elastic.co/u/bfarr11)\
**Post date:** [May 19, 2024, 3:06am UTC](https://discuss.elastic.co/t/3-nodes-7-17-on-a-single-server/359410/7 "2024-05-19T03:06:53Z")

</div>

Thanks.

I did a separate service file trying to get the first instance running. I set all the variables properly. There is something not exposed that still points the configuration directory to /etc/elasticsearch/.

I'll try the 3 separate installs.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [May 19, 2024, 3:34am UTC](https://discuss.elastic.co/t/3-nodes-7-17-on-a-single-server/359410/8 "2024-05-19T03:34:30Z")

</div>

Share the service file

---

<div class="post-metadata">

**Author:** ![bfarr11](https://avatars.discourse-cdn.com/v4/letter/b/77aa72/32.png) [@bfarr11](https://discuss.elastic.co/u/bfarr11)\
**Post date:** [May 20, 2024, 1:47am UTC](https://discuss.elastic.co/t/3-nodes-7-17-on-a-single-server/359410/9 "2024-05-20T01:47:31Z")

</div>

I got it working with .gz file.

I have all 3 nodes up and running on same server and it is working very well.
