# Hot warm architecture

**URL:** <https://discuss.elastic.co/t/hot-warm-architecture/135217>\
**Category:** Elasticsearch\
**Created:** [June 9, 2018, 9:16am UTC](https://discuss.elastic.co/t/hot-warm-architecture/135217 "2018-06-09T09:16:45Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![br14nb0](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/br14nb0/32/28814_2.png) [@br14nb0](https://discuss.elastic.co/u/br14nb0)\
**Post date:** [June 9, 2018, 9:16am UTC](https://discuss.elastic.co/t/hot-warm-architecture/135217/1 "2018-06-09T09:16:45Z")

</div>

I checked out the Hot warm architecture, so I have some questions.

1. Can Hot or Warm node is an eligible master-data node ?
2. I intend to implement it with 4 nodes, including 2 Hot nodes as eligible master-data note and 2 Warm node as data node. Is it a good idea ?  
Thanks

---

<div class="post-metadata">

**Author:** ![br14nb0](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/br14nb0/32/28814_2.png) [@br14nb0](https://discuss.elastic.co/u/br14nb0)\
**Post date:** [June 11, 2018, 2:46am UTC](https://discuss.elastic.co/t/hot-warm-architecture/135217/2 "2018-06-11T02:46:00Z")

</div>

. anyone can help me ?

---

<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:** [June 11, 2018, 6:36am UTC](https://discuss.elastic.co/t/hot-warm-architecture/135217/3 "2018-06-11T06:36:24Z")

</div>

> [@br14nb0](#):
>
> Can Hot or Warm node is an eligible master-data node ?

Yes, they can. But as hot nodes in particular can get very heavily loaded, they may not be ideal as master nodes.

> [@br14nb0](#):
>
> I intend to implement it with 4 nodes, including 2 Hot nodes as eligible master-data note and 2 Warm node as data node. Is it a good idea ?

You should always aim to have at least 3 master-eligible nodes in a cluster, so I would recommend making all of them master-eligible and set `minimum_master_nodes` to `3` as per [these guidelines](https://www.elastic.co/guide/en/elasticsearch/reference/6.2/modules-node.html#split-brain).

If you realise the cluster is having problems with master nodes getting re-elected frequently, you may want to introduce at least one smaller dedicated master node.

---

<div class="post-metadata">

**Author:** ![br14nb0](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/br14nb0/32/28814_2.png) [@br14nb0](https://discuss.elastic.co/u/br14nb0)\
**Post date:** [June 11, 2018, 12:18pm UTC](https://discuss.elastic.co/t/hot-warm-architecture/135217/4 "2018-06-11T12:18:37Z")

</div>

Thanks for useful info

---

<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 9, 2018, 12:18pm UTC](https://discuss.elastic.co/t/hot-warm-architecture/135217/5 "2018-07-09T12:18:38Z")

</div>

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