# Data node as Master Node

**URL:** https://discuss.elastic.co/t/data-node-as-master-node/166627
**Category:** Elasticsearch
**Created:** [January 31, 2019, 6:37pm UTC](https://discuss.elastic.co/t/data-node-as-master-node/166627 "2019-01-31T18:37:20Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![aniaks](https://avatars.discourse-cdn.com/v4/letter/a/ac8455/32.png) [@aniaks](https://discuss.elastic.co/u/aniaks)
#### Post date: [January 31, 2019, 6:37pm UTC](https://discuss.elastic.co/t/data-node-as-master-node/166627/1 "2019-01-31T18:37:20Z")

</div>

Is it good to have a cluster with the following

2 Ingest Nodes (doesnt do anything except routing the bulk request)  
5 Data nodes (Also as master nodes)  
1 coord node

I see in documentation - there should be dedicated master nodes. Let me know the best practice.

---

<div class="post-metadata">

### Author: ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [January 31, 2019, 7:07pm UTC](https://discuss.elastic.co/t/data-node-as-master-node/166627/2 "2019-01-31T19:07:32Z")

</div>

The 2 ingest nodes won't be then ingest nodes but coordinating nodes.  
Ingest nodes are meant to execute an ingest pipeline which you does not seem to use here.

Dedicated master nodes are indeed a plus. Specifically if you have big cluster state. But not mandatory for "small" clusters.

---

<div class="post-metadata">

### Author: ![aniaks](https://avatars.discourse-cdn.com/v4/letter/a/ac8455/32.png) [@aniaks](https://discuss.elastic.co/u/aniaks)
#### Post date: [January 31, 2019, 7:13pm UTC](https://discuss.elastic.co/t/data-node-as-master-node/166627/3 "2019-01-31T19:13:23Z")

</div>

Thanks much David !

would it make a difference to convert the ingest to coordinator node ? if we are just using it for sending the data to data nodes.

Also if i understood right - if cluster has more than 10+ data nodes its good to have dedicated master nodes. where the recommendation is 3 master nodes.

---

<div class="post-metadata">

### Author: ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [January 31, 2019, 7:26pm UTC](https://discuss.elastic.co/t/data-node-as-master-node/166627/4 "2019-01-31T19:26:13Z")

</div>

> [@aniaks](#):
>
> would it make a difference to convert the ingest to coordinator node ?

I'm unsure if you need 3 coordinating nodes. That depends on what you are doing and how much data you are ingesting per day.

> Also if i understood right - if cluster has more than 10+ data nodes its good to have dedicated master nodes. where the recommendation is 3 master nodes.

Yes.

May I suggest you look at the following resources about sizing:

> **[Quantitative Cluster Sizing](https://www.elastic.co/elasticon/conf/2016/sf/quantitative-cluster-sizing)**

> **[How many shards should I have in my Elasticsearch cluster?](https://www.elastic.co/blog/how-many-shards-should-i-have-in-my-elasticsearch-cluster)**

> **[NetSecureDay: Managing your Black Friday Logs](https://speakerdeck.com/elastic/netsecureday-managing-your-black-friday-logs)**
>
> Surveiller une application complexe n’est pas une tâche aisée, mais avec les bons outils, ce n’est pas si sorcier. Néanmoins, des périodes fortes telles que les opérations de type « Black Friday » (Vendredi noir) ou période de Noël peuvent pousser...

[![](https://us1.discourse-cdn.com/elastic/original/3X/7/c/7c2edebd5bac194c58a5df87ede6872cb41d61a8.jpeg "Managing your Black Friday Logs, Pablo Musa, Elastic, TechSummit Amsterdam") ](https://www.youtube.com/watch?v=ilP7tG6tabI)

And [https://www.elastic.co/webinars/using-rally-to-get-your-elasticsearch-cluster-size-right](https://www.elastic.co/webinars/using-rally-to-get-your-elasticsearch-cluster-size-right)

---

<div class="post-metadata">

### Author: ![aniaks](https://avatars.discourse-cdn.com/v4/letter/a/ac8455/32.png) [@aniaks](https://discuss.elastic.co/u/aniaks)
#### Post date: [January 31, 2019, 7:32pm UTC](https://discuss.elastic.co/t/data-node-as-master-node/166627/5 "2019-01-31T19:32:53Z")

</div>

Yes we need 3 ingest nodes, sometimes we see one ingest node receives 95% of the load and that causes the indexing rate to go down.

Is there a better way to handle this situation ?

---

<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 31, 2019, 8:02pm UTC](https://discuss.elastic.co/t/data-node-as-master-node/166627/6 "2019-01-31T20:02:46Z")

</div>

Looks this

> [@Simple elasticsearch database designe help](https://discuss.elastic.co/t/simple-elasticsearch-database-designe-help/164935/11):
>
> oh ok I misunderstood. index name is Tapes-2019, then Tapes-2020 got it

I ask pretty much same question earlier

---

<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 28, 2019, 8:02pm UTC](https://discuss.elastic.co/t/data-node-as-master-node/166627/7 "2019-02-28T20:02:55Z")

</div>

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