# Can Active Master election priority be decided?

**URL:** <https://discuss.elastic.co/t/can-active-master-election-priority-be-decided/149669>\
**Category:** Elasticsearch\
**Created:** [September 24, 2018, 12:32pm UTC](https://discuss.elastic.co/t/can-active-master-election-priority-be-decided/149669 "2018-09-24T12:32:27Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![pokaleshrey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pokaleshrey/32/48680_2.png) [@pokaleshrey](https://discuss.elastic.co/u/pokaleshrey)\
**Post date:** [September 24, 2018, 12:32pm UTC](https://discuss.elastic.co/t/can-active-master-election-priority-be-decided/149669/1 "2018-09-24T12:32:27Z")

</div>

**My setup:**  
1 Master node: Low RAM and CPU machine  
2 Coordinating nodes (also eligible masters): Highly configured machines  
2 Data nodes (One Replica)(RAID-0)

**Issue:**  
By the master election process, any of the Master or my coordinating nodes is elected as active master.  
I send all my indexing and searching requests to both coordinating nodes.  
If coordinating node is elected as master, it starts performing 2 responsibilities, one is master and other is coordinating.

**Question:**  
Is there an option to tell ES explicitly that my 'Master node' above should be the initial active master, when my cluster starts. And thereafter it may give priority to any of coordinating nodes ??  
This way initially, unless there is problem with 'Master node', at least my master responsibility will be carried out by dedicated master node and coordinating responsibility will be with Coordinating nodes.

---

<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:** [September 24, 2018, 12:45pm UTC](https://discuss.elastic.co/t/can-active-master-election-priority-be-decided/149669/2 "2018-09-24T12:45:02Z")

</div>

No, this is currently not possible.

---

<div class="post-metadata">

**Author:** ![pokaleshrey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pokaleshrey/32/48680_2.png) [@pokaleshrey](https://discuss.elastic.co/u/pokaleshrey)\
**Post date:** [September 25, 2018, 5:17am UTC](https://discuss.elastic.co/t/can-active-master-election-priority-be-decided/149669/3 "2018-09-25T05:17:43Z")

</div>

Ok. @Christian_Dahlqvist: If my coordinating nodes have too much load, does ES, on the fly, elect a master which has low amount of load ?

---

<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:** [September 25, 2018, 5:22am UTC](https://discuss.elastic.co/t/can-active-master-election-priority-be-decided/149669/4 "2018-09-25T05:22:09Z")

</div>

As far as I know, load is not taken into account during the election process. Assuming the hosts with your coordinating nodes are powerful enough, you may benefit from running two nodes on each - one dedicated master node with small heap and the current coordinating node. This would give you three dedicated master nodes, which should not receive any traffic but be left to manage the cluster. Even better would naturally be to have three dedicated master nodes on separate hosts.

---

<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:** [October 23, 2018, 5:22am UTC](https://discuss.elastic.co/t/can-active-master-election-priority-be-decided/149669/5 "2018-10-23T05:22:11Z")

</div>

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