# Single Server Single Node vs Single Server Multiple Node

**URL:** <https://discuss.elastic.co/t/single-server-single-node-vs-single-server-multiple-node/324081>\
**Category:** Elasticsearch\
**Created:** [January 27, 2023, 2:38am UTC](https://discuss.elastic.co/t/single-server-single-node-vs-single-server-multiple-node/324081 "2023-01-27T02:38:18Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![sramana235](https://avatars.discourse-cdn.com/v4/letter/s/bbce88/32.png) [@sramana235](https://discuss.elastic.co/u/sramana235)\
**Post date:** [January 27, 2023, 2:38am UTC](https://discuss.elastic.co/t/single-server-single-node-vs-single-server-multiple-node/324081/1 "2023-01-27T02:38:18Z")

</div>

As the title suggests, I wonder if it is better to configure a single node or multiple nodes when configuring a node on a single server.

I understood that the reason for configuring multiple nodes can have the advantages of performance and backup by distributing data.

However, I understood that this case is a case of multiple servers, but if it is a single server, can it have the following advantages if it is configured as multiple nodes?

If that happens, I wonder if I can use the replica shard in the single node.

---

<div class="post-metadata">

**Author:** ![Rios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rios/32/95745_2.png) [@Rios](https://discuss.elastic.co/u/Rios)\
**Post date:** [January 27, 2023, 6:57am UTC](https://discuss.elastic.co/t/single-server-single-node-vs-single-server-multiple-node/324081/2 "2023-01-27T06:57:18Z")

</div>

My opinion:

Single node adv:

- simple for configuration and maintenance
- easy to monitor
- less storage, no replica
- cheap
- internal authentication
- excellent for indices 1-50 GB, or a storage in total to 1 TB, good for test environments, big small data 🙂

Disadvantages:

- no replica
- no fail tolerance
- no ILM
- no data roles
- ingestion node shouldn't be avoided, it's better to use Logstash on a separated host
- avoid complex queries/dashboards

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [January 27, 2023, 7:17am UTC](https://discuss.elastic.co/t/single-server-single-node-vs-single-server-multiple-node/324081/3 "2023-01-27T07:17:16Z")

</div>

> [@Rios](#):
>
> Disadvantages:
> 
> - no replica
> - no fail tolerance

If you only have one physical machine, a replica is kind of a waste of resources so "no replica" is an advantage IMO, and "no fail tolerance" applies to both options.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [January 27, 2023, 7:19am UTC](https://discuss.elastic.co/t/single-server-single-node-vs-single-server-multiple-node/324081/4 "2023-01-27T07:19:50Z")

</div>

> [@sramana235](#):
>
> However, I understood that this case is a case of multiple servers, but if it is a single server, can it have the following advantages if it is configured as multiple nodes?

If your node has multiple disks you can configure multiple Elasticsearch nodes to each use a different disk, which can protect you from disk failures if you have a replica shard configured. The drawback here is that you will use double the storage space to store each shard twice.

If you have a really large node with multiple disks it may therefore make sense to run multiple nodes on it, but I would otherwise generally recommend against it due to the overhead it adds. It is better to deploy multiple nodes across multiple servers as that would allow the cluster to continue operating if a node goes down.

---

<div class="post-metadata">

**Author:** ![Rios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rios/32/95745_2.png) [@Rios](https://discuss.elastic.co/u/Rios)\
**Post date:** [January 27, 2023, 10:06am UTC](https://discuss.elastic.co/t/single-server-single-node-vs-single-server-multiple-node/324081/5 "2023-01-27T10:06:16Z")

</div>

> [@DavidTurner](#):
>
> If you only have one physical machine, a replica is kind of a waste of resources so "no replica" is an advantage IMO, and "no fail tolerance" applies to both options.

Yes, the single-node without replica is just a feature. From point of CIA, 3nodes are better solution.

---

<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:** [February 24, 2023, 10:06am UTC](https://discuss.elastic.co/t/single-server-single-node-vs-single-server-multiple-node/324081/6 "2023-02-24T10:06:22Z")

</div>

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