# Dedicated master - quorum and recovery settings

**URL:** https://discuss.elastic.co/t/dedicated-master-quorum-and-recovery-settings/34893
**Category:** Elasticsearch
**Created:** [November 18, 2015, 8:00am UTC](https://discuss.elastic.co/t/dedicated-master-quorum-and-recovery-settings/34893 "2015-11-18T08:00:35Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Chris\_Fraschetti](https://avatars.discourse-cdn.com/v4/letter/c/9d8465/32.png) [@Chris\_Fraschetti](https://discuss.elastic.co/u/Chris_Fraschetti)
#### Post date: [November 18, 2015, 8:00am UTC](https://discuss.elastic.co/t/dedicated-master-quorum-and-recovery-settings/34893/1 "2015-11-18T08:00:35Z")

</div>

My cluster has finally reached the size/complexity where I'm ready to roll out dedicated master nodes.

What I haven't been able to 100% nail down is what settings belong on the data nodes vs. what belong on the master nodes.

Here are the settings in question:

gateway.expected\_master\_nodes  
gateway.recover\_after\_nodes  
gateway.expected\_nodes  
gateway.recover\_after\_time

My question is simply - which of these settings need to exist on the data nodes, master nodes, or both?

My assumption would be:

**Data nodes only**  
gateway.recover\_after\_nodes  
gateway.expected\_nodes  
gateway.recover\_after\_time

**Master nodes only**  
gateway.expected\_master\_nodes

While I've found a decent amount of material encouraging the use of dedicated masters, the documentation for how to pull that off (correctly) is a bit lacking.

Thanks in advance!

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [November 18, 2015, 10:27am UTC](https://discuss.elastic.co/t/dedicated-master-quorum-and-recovery-settings/34893/2 "2015-11-18T10:27:40Z")

</div>

You need the same settings on all the nodes 😄

Fair point around the docs, will see what we can do to fix it!

---

<div class="post-metadata">

### Author: ![Chris\_Fraschetti](https://avatars.discourse-cdn.com/v4/letter/c/9d8465/32.png) [@Chris\_Fraschetti](https://discuss.elastic.co/u/Chris_Fraschetti)
#### Post date: [November 18, 2015, 9:44pm UTC](https://discuss.elastic.co/t/dedicated-master-quorum-and-recovery-settings/34893/3 "2015-11-18T21:44:23Z")

</div>

Thanks. Every node it is.

I've seen a lot of improvements in the docs over the past year or so, I think a few more "here's what configuration settings apply to what nodes in the scenarios we've been describing" would go a long way.

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [November 19, 2015, 12:49am UTC](https://discuss.elastic.co/t/dedicated-master-quorum-and-recovery-settings/34893/4 "2015-11-19T00:49:46Z")

</div>

Understood, problem is that there is a _lot_ of different scenarios.  
However when it comes to basic N node deployments this should be easier to do.

---

<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: [July 5, 2017, 11:37pm UTC](https://discuss.elastic.co/t/dedicated-master-quorum-and-recovery-settings/34893/5 "2017-07-05T23:37:24Z")

</div>


