# Retiring indexes from SSDs to HDDs

**URL:** <https://discuss.elastic.co/t/retiring-indexes-from-ssds-to-hdds/67851>\
**Category:** Elasticsearch\
**Created:** [December 2, 2016, 11:59am UTC](https://discuss.elastic.co/t/retiring-indexes-from-ssds-to-hdds/67851 "2016-12-02T11:59:41Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![wptq](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wptq/32/13552_2.png) [@wptq](https://discuss.elastic.co/u/wptq)\
**Post date:** [December 2, 2016, 11:59am UTC](https://discuss.elastic.co/t/retiring-indexes-from-ssds-to-hdds/67851/1 "2016-12-02T11:59:41Z")

</div>

Hi all,

We've got a ELK cluster running ES 5.0 for logs indexing, collecting them from Kafka using Logstash. Each node has 1TB in SSDs and 2TB in HDDs. At the moment, we're only using SSD volumes with Elasticsearch.

However, we only need a certain amount of data being stored on SSDs as hot data, then we would like to move it to HDDs. So classically, retiring cold data to a slower storage.

I found tips on how to make it, however I wanted to find out if there are good practices of achieving it, or if there is something recommended?

Any help appreciated!  
Wojtek

---

<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:** [December 2, 2016, 12:06pm UTC](https://discuss.elastic.co/t/retiring-indexes-from-ssds-to-hdds/67851/2 "2016-12-02T12:06:41Z")

</div>

[This blog post](https://www.elastic.co/blog/hot-warm-architecture) outlines how this works in a Hot/Warm architecture. This does however require the different types of storage to belong to different Elasticsearch nodes that can be tagged appropriately. If you have the two types of storage on the same hosts, you may therefore need to run multiple Elasticsearch nodes per host.

---

<div class="post-metadata">

**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\
**Post date:** [December 2, 2016, 2:48pm UTC](https://discuss.elastic.co/t/retiring-indexes-from-ssds-to-hdds/67851/3 "2016-12-02T14:48:16Z")

</div>

The Curator example in that blog post uses 3.0, which is outdated. The current release of Curator is 4.2.3, and the allocation action documentation is [here](https://www.elastic.co/guide/en/elasticsearch/client/curator/current/allocation.html).

---

<div class="post-metadata">

**Author:** ![wptq](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wptq/32/13552_2.png) [@wptq](https://discuss.elastic.co/u/wptq)\
**Post date:** [December 12, 2016, 9:14am UTC](https://discuss.elastic.co/t/retiring-indexes-from-ssds-to-hdds/67851/4 "2016-12-12T09:14:51Z")

</div>

Thanks you both @Christian_Dahlqvist and @theuntergeek. That's one of the approaches we were thinking of using. I thought there might be another ways of achieving this.

We'll test it and I will happily share our outcomes.

---

<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:** [January 9, 2017, 9:15am UTC](https://discuss.elastic.co/t/retiring-indexes-from-ssds-to-hdds/67851/5 "2017-01-09T09:15:15Z")

</div>

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