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.
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.
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.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.