# Force cluster to elect new master node

**URL:** <https://discuss.elastic.co/t/force-cluster-to-elect-new-master-node/352094>\
**Category:** Elasticsearch\
**Created:** [January 30, 2024, 1:53pm UTC](https://discuss.elastic.co/t/force-cluster-to-elect-new-master-node/352094 "2024-01-30T13:53:29Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![sourcreamnormanbates](https://avatars.discourse-cdn.com/v4/letter/s/f05b48/32.png) [@sourcreamnormanbates](https://discuss.elastic.co/u/sourcreamnormanbates)\
**Post date:** [January 30, 2024, 1:53pm UTC](https://discuss.elastic.co/t/force-cluster-to-elect-new-master-node/352094/1 "2024-01-30T13:53:29Z")

</div>

I added a master-only node to my cluster.  
How do I trigger the active master role to the new node?  
I want to leave at least 2 of my data nodes as eligible masters, but have my cluster prioritize use of the dedicated master.

---

<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 30, 2024, 1:55pm UTC](https://discuss.elastic.co/t/force-cluster-to-elect-new-master-node/352094/2 "2024-01-30T13:55:24Z")

</div>

There is no need to do this. You should not care which of the master-eligible nodes is the active master as this can change over time. The active master node does very little in most clusters so will not add a lot of load.

If you are concerned about one of the master-data nodes being elected as the master and have seen some impact you should look to have 3 dedicated master nodes instead.

---

<div class="post-metadata">

**Author:** ![sourcreamnormanbates](https://avatars.discourse-cdn.com/v4/letter/s/f05b48/32.png) [@sourcreamnormanbates](https://discuss.elastic.co/u/sourcreamnormanbates)\
**Post date:** [January 30, 2024, 2:01pm UTC](https://discuss.elastic.co/t/force-cluster-to-elect-new-master-node/352094/3 "2024-01-30T14:01:27Z")

</div>

The currently elected master node is also an ingest for Elastic Agent clients so CPU is always really high (90-100%).  
Elastic support recommended a dedicated master to improve performance, but now it's just sitting there pretty much doing nothing.

---

<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 30, 2024, 2:14pm UTC](https://discuss.elastic.co/t/force-cluster-to-elect-new-master-node/352094/4 "2024-01-30T14:14:49Z")

</div>

You should load balance the indexing load across the two data nodes so they are reasonably evenly loaded and not send all traffic to just one of the 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 27, 2024, 2:15pm UTC](https://discuss.elastic.co/t/force-cluster-to-elect-new-master-node/352094/5 "2024-02-27T14:15:41Z")

</div>

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