# Separate data and metadata

**URL:** https://discuss.elastic.co/t/separate-data-and-metadata/248531
**Category:** Elasticsearch
**Created:** [September 14, 2020, 1:20pm UTC](https://discuss.elastic.co/t/separate-data-and-metadata/248531 "2020-09-14T13:20:09Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Oleg\_Ruchovets](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/oleg_ruchovets/32/60137_2.png) [@Oleg\_Ruchovets](https://discuss.elastic.co/u/Oleg_Ruchovets)
#### Post date: [September 14, 2020, 1:20pm UTC](https://discuss.elastic.co/t/separate-data-and-metadata/248531/1 "2020-09-14T13:20:09Z")

</div>

Hello.  
In Hadoop echo system and some other solution: data and metadata are stored separately. For Hadoop, there are master nodes to store metadata.

Question: does Elasticsearch have similar architecture? I mean is there metadata and data separation or ES hold data and metadata as part of the same JSON document?

Thanks.

---

<div class="post-metadata">

### Author: ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [September 14, 2020, 1:52pm UTC](https://discuss.elastic.co/t/separate-data-and-metadata/248531/2 "2020-09-14T13:52:56Z")

</div>

In Elasticsearch the master-eligible nodes are responsible for the cluster metadata, whereas the data nodes are responsible for the data. A single node can do both roles, or you can separate them. See [these docs](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html#node-roles) for more information.

---

<div class="post-metadata">

### Author: ![Oleg\_Ruchovets](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/oleg_ruchovets/32/60137_2.png) [@Oleg\_Ruchovets](https://discuss.elastic.co/u/Oleg_Ruchovets)
#### Post date: [September 14, 2020, 2:16pm UTC](https://discuss.elastic.co/t/separate-data-and-metadata/248531/3 "2020-09-14T14:16:50Z")

</div>

Ok, Thank @DavidTurner for the quick answer.

Is it a best practice to separate the master node from data nodes?  
In case of a master crashed elastic will elect a new master, right? what will be in this case with metadata? Should master machine configuration be more memory / CPU / disk intensive comparing to the data node?

Thanks

---

<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: [September 14, 2020, 10:17pm UTC](https://discuss.elastic.co/t/separate-data-and-metadata/248531/4 "2020-09-14T22:17:02Z")

</div>

> [@Oleg\_Ruchovets](#):
>
> Is it a best practice to separate the master node from data nodes?

Yes.

> [@Oleg\_Ruchovets](#):
>
> In case of a master crashed elastic will elect a new master, right? what will be in this case with metadata?

Yes. All nodes in the cluster hold the cluster state.

> [@Oleg\_Ruchovets](#):
>
> Should master machine configuration be more memory / CPU / disk intensive comparing to the data node?

No, you might even be able to go with less.

---

<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 12, 2020, 10:17pm UTC](https://discuss.elastic.co/t/separate-data-and-metadata/248531/5 "2020-10-12T22:17:08Z")

</div>

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