Dedicated master-eligible nodes

(Laurentiu Soica) #1


When talking about nodes, the ES documentation says: "To ensure that your master node is stable and not under pressure, it is a good idea in a bigger cluster to split the roles between dedicated master-eligible nodes and dedicated data nodes."

Now the question is what means a "bigger cluster"; how to decide if your cluster is too big to share roles on same nodes and needs dedicated mater-eligible nodes ?


(Christian Dahlqvist) #2

It is not necessarily just a question about the size of the cluster, but also the load it is under. If you have combined master/data nodes, all nodes need to have enough resources available to handle master duties. Once nodes start getting under pressure, e.g. due to increased data volumes or traffic spikes, resulting in longer GC, the risk of suffering from instability increases.

Clusters with 3-5 data nodes can often get away without dedicated master nodes unless load is heavy or unpredictable, but there is no hard limit to what constitutes a 'bigger' cluster.

Another consideration is the speed at which you are expanding the cluster. Changing the number of master eligible nodes in a cluster means that the minimum_master_nodeds setting also need to be updated every time. If you need to be able to easily scale the cluster up or down, this is generally a lot easier with a fixed number of dedicated master nodes.

(Laurentiu Soica) #3

Ok, so basically if I cannot predict/limit the traffic, the best way is to go with dedicated master nodes, right ?

Regarding the minimum_master_nodes updates, I only plan for upscale. Are there any technical difficulties in updating the parameter ? e.g. like handling the race between updating the param and adding a new node?


(system) #4

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