I want to know the pros and cons

Elastic Stack Elasticsearch
1

Hi, my name is Eddy Kim.
I'm not good at English. Please look at this.

We're going to build our own ElasticSearch infrastructure, and we're going to buy a server soon.

Our systems are not big data, but indexing performance is very important. I'm going to make 3 to 5 nodes. I want to know the pros and cons of four methods. I don't want to be overly engineering.

I don't know if I need a client node.
Why client nodes are typically required?

If it's true that we don't need a client node...
I'm looking at number1 and number4.

Number1 and number4...
I'm not sure if the indexing performance is very different.

Anyway, for a little bit of faster performance, I'd like to make a final decision with Number1, which is separated from Master Node, but I'm not sure if it's a valid decision.

Again, I don't want to over-engineer!!!

1
1.PNG764×584 38.3 KB

2
2.PNG610×628 30.2 KB

2

Option 4 is generally the recommended starting point.

3

I thank you from the bottom of my heart.

We have decided to proceed to Option4 for your advice.

However, I still want to know. I'd like to know the pros and cons of Option 1-4.

4

Indexing performance will likely be limited by the data nodes so adding all the other node types may not give you much. You should also always aim to have at least 3 master eligible nodes which a few options do not. Adding 3 dedicated master nodes may be good down the line if your master/data nodes are under very heavy load, but you should then not send requests through them and leave them to manage the cluster.

5

Thank you. @Christrian_Dahlqvist

Your advice has been very helpful to me.

6

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