# ES node storage size mixing?

**URL:** https://discuss.elastic.co/t/es-node-storage-size-mixing/223214
**Category:** Elasticsearch
**Created:** [March 11, 2020, 8:25pm UTC](https://discuss.elastic.co/t/es-node-storage-size-mixing/223214 "2020-03-11T20:25:07Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![EricMM](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ericmm/32/64264_2.png) [@EricMM](https://discuss.elastic.co/u/EricMM)
#### Post date: [March 11, 2020, 8:25pm UTC](https://discuss.elastic.co/t/es-node-storage-size-mixing/223214/1 "2020-03-11T20:25:07Z")

</div>

We have a few year old cluster of 15 servers (2 ES nodes per server) with 8TBs of local storage each, but are we running low on space and having to cut back on retention. I want to add 80TBs to increase our total storage from 120TBs to 200TBs, but we are limited on physical rack space, so is it possible to add 4 servers with 20TBs of space each? (all numbers usable space after hardware RAID)

I've heard that Elasticsearch likes each ES node to be configured with the same amount of storage, is this true? I couldn't locate any documentation that explicitly states this. Would ES balance the shards ok across the node storage differences, or would 12 TBs be "wasted" on the new servers?

---

<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: [March 11, 2020, 8:37pm UTC](https://discuss.elastic.co/t/es-node-storage-size-mixing/223214/2 "2020-03-11T20:37:14Z")

</div>

You can easily do this if you setup hot/warm/cold tiering using [ILM](https://www.elastic.co/guide/en/elasticsearch/reference/current/ilm-settings.html). Where your nodes with more storage would be cold nodes.

---

<div class="post-metadata">

### Author: ![EricMM](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ericmm/32/64264_2.png) [@EricMM](https://discuss.elastic.co/u/EricMM)
#### Post date: [March 11, 2020, 8:43pm UTC](https://discuss.elastic.co/t/es-node-storage-size-mixing/223214/3 "2020-03-11T20:43:30Z")

</div>

Unfortunately I don't think that would work for us. We have a lot of hot data, and we're not allowed to keep it past a certain amount of time, so we don't really have any cold data.

---

<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: [March 11, 2020, 8:47pm UTC](https://discuss.elastic.co/t/es-node-storage-size-mixing/223214/4 "2020-03-11T20:47:36Z")

</div>

If you want to think of it another way - standard and dense node types. Then you can store more data on the dense ones over the standard ones.

Hot/warm/cold is a logical construct that you can repurpose for this type of thing too.

---

<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: [April 8, 2020, 8:47pm UTC](https://discuss.elastic.co/t/es-node-storage-size-mixing/223214/5 "2020-04-08T20:47:38Z")

</div>

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