# More master node?

**URL:** <https://discuss.elastic.co/t/more-master-node/323348>\
**Category:** Elasticsearch\
**Created:** [January 17, 2023, 4:30pm UTC](https://discuss.elastic.co/t/more-master-node/323348 "2023-01-17T16:30:38Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Verdugo\_Gonzalo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/verdugo_gonzalo/32/37680_2.png) [@Verdugo\_Gonzalo](https://discuss.elastic.co/u/Verdugo_Gonzalo)\
**Post date:** [January 17, 2023, 4:30pm UTC](https://discuss.elastic.co/t/more-master-node/323348/1 "2023-01-17T16:30:38Z")

</div>

Hello everyone, I explain my context.  
I am designing an architecture with 18 nodes where everyone can be master (of the 18 nodes, only 1 master remains) if necessary, but I feel that 1 for 17 is too little and I want to put 3 masters.  
Is there the possibility of adding N amount of master without having dedicated ones?  
I am using version 8.6

```auto

cluster.name: MYCLUSTER
discovery.seed_hosts: ["123.188.49.31", "123.188.49.33", "123.188.49.34", "123.188.49.76", "123.188.49.79", "123.188.49.80", "123.188.49.87", "123.188.49.144", "123.188.49.147", "123.176.49.21", "123.176.49.23", "123.176.49.24", "123.176.49.31", "123.176.49.77", "123.176.49.78", "123.176.49.80", "123.176.49.81", "123.176.49.82"]
cluster.initial_master_nodes: ["Node01", "Node02", "Node03", "Node04", "Node05", "Node06", "Node07", "Node08", "Node09", "Node10", "Node11", "Node12", "Node13", "Node14", "Node15", "Node16", "Node17", "Node18"]

```

---

<div class="post-metadata">

**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\
**Post date:** [January 17, 2023, 5:03pm UTC](https://discuss.elastic.co/t/more-master-node/323348/2 "2023-01-17T17:03:52Z")

</div>

I don't see a reason to have these many master.  
moret master you have more syncing will happen between them as they have to keep each other up-to-date about all information.

I would keep 3 or max 5 master as cluster will still survive if two of them goes down togather.

also cluster.initial.master\_nodes have to be used only one time when you create a cluster. once cluster is created you don't need that. you have all the node listed there.

---

<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:** [January 17, 2023, 5:26pm UTC](https://discuss.elastic.co/t/more-master-node/323348/3 "2023-01-17T17:26:44Z")

</div>

> [@Verdugo\_Gonzalo](#):
>
> I am designing an architecture with 18 nodes where everyone can be master (of the 18 nodes, only 1 master remains) if necessary, but I feel that 1 for 17 is too little and I want to put 3 masters.

Can you give more context of what you want to achieve with this architecture?

> [@Verdugo\_Gonzalo](#):
>
> I feel that 1 for 17 is too little and I want to put 3 masters.

Why you feel that? On a elasticsearch cluster only **one** node will be the master, you can have N master-eligible nodes, but only one will be the master, if the master node goes down for any reason, another master-eligible node will assume the role.

The best approach, and the recommendation, is to have dedicated master, at least 3 dedicated master nodes.

---

<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 17, 2023, 5:38pm UTC](https://discuss.elastic.co/t/more-master-node/323348/4 "2023-01-17T17:38:28Z")

</div>

> [@leandrojmp](#):
>
> The best approach, and the recommendation, is to have dedicated master, at least 3 dedicated master nodes.

Specifically, the official docs say so [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/high-availability-cluster-small-clusters.html#high-availability-cluster-design-three-plus-nodes):

> # Clusters with more than three nodes
> 
> ...  
> However, it is good practice to limit the number of master-eligible nodes in the cluster to three.

---

<div class="post-metadata">

**Author:** ![Verdugo\_Gonzalo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/verdugo_gonzalo/32/37680_2.png) [@Verdugo\_Gonzalo](https://discuss.elastic.co/u/Verdugo_Gonzalo)\
**Post date:** [January 17, 2023, 7:53pm UTC](https://discuss.elastic.co/t/more-master-node/323348/5 "2023-01-17T19:53:41Z")

</div>

> [@leandrojmp](#):
>
> Can you give more context of what you want to achieve with this architecture?

Thank you very much for your answer.  
Well, I have a customer who has 18 nodes ready to create a licensed elasticsearch cluster. I had thought of a design where any of the 18 nodes could be master but consulting the elastic documentation and reviewing the forum I found that the vast majority used more than 1 master node.  
I raised the cluster and put the configuration in [checkups.opster.com](http://checkups.opster.com) where it also recommended having at least 3 master nodes

> [@leandrojmp](#):
>
> On a elasticsearch cluster only **one** node will be the master

So the only way to have more than 1 master node is to make it dedicated, right?  
I wanted to find a way to automatically choose 2 or 3 master nodes instead of just 1.

---

<div class="post-metadata">

**Author:** ![Verdugo\_Gonzalo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/verdugo_gonzalo/32/37680_2.png) [@Verdugo\_Gonzalo](https://discuss.elastic.co/u/Verdugo_Gonzalo)\
**Post date:** [January 17, 2023, 7:54pm UTC](https://discuss.elastic.co/t/more-master-node/323348/6 "2023-01-17T19:54:45Z")

</div>

> [@DavidTurner](#):
>
> Specifically, the official docs say so [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/high-availability-cluster-small-clusters.html#high-availability-cluster-design-three-plus-nodes):

Thank you very much @DavidTurner @elasticforme , I will continue reading the documentation to find a good solution.

---

<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:** [January 17, 2023, 8:02pm UTC](https://discuss.elastic.co/t/more-master-node/323348/7 "2023-01-17T20:02:54Z")

</div>

> [@Verdugo\_Gonzalo](#):
>
> So the only way to have more than 1 master node is to make it dedicated, right?  
> I wanted to find a way to automatically choose 2 or 3 master nodes instead of just 1.

Your cluster will only have **one** node acting as the master node, this is how elasticsearch works, you will have other _master eligible_ nodes that can assume the role of the master node if the current master fails.

For example, if you have 3 dedicated master nodes, only one will be the elected master, the other two will be in stand-by to assume the role in case of a failure, the same applies to N number of master eligible nodes.

---

<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 14, 2023, 8:03pm UTC](https://discuss.elastic.co/t/more-master-node/323348/8 "2023-02-14T20:03:49Z")

</div>

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