# Data Relocation

**URL:** https://discuss.elastic.co/t/data-relocation/195615
**Category:** Elasticsearch
**Created:** [August 17, 2019, 6:47pm UTC](https://discuss.elastic.co/t/data-relocation/195615 "2019-08-17T18:47:44Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Diego\_Jota](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/diego_jota/32/50813_2.png) [@Diego\_Jota](https://discuss.elastic.co/u/Diego_Jota)
#### Post date: [August 17, 2019, 6:47pm UTC](https://discuss.elastic.co/t/data-relocation/195615/1 "2019-08-17T18:47:44Z")

</div>

Hello, I am storing my data on a disk, for example, in C.  
When this disk reaches 90%, I want the new data entered to be allocated on disk D. Is there any way to configure this setting?

---

<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: [August 17, 2019, 7:13pm UTC](https://discuss.elastic.co/t/data-relocation/195615/2 "2019-08-17T19:13:48Z")

</div>

Elasticsearch can use multiple data paths, but each shard will be located to a single path and Elasticsearch will not move shards between paths. It will therefore not behave as you describe.

If you are creating time based indices, you could add the new disk to the data path and new shards should get allocated there. If you are not creating new indices changing the path will probably not help.

---

<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: [September 14, 2019, 7:26pm UTC](https://discuss.elastic.co/t/data-relocation/195615/3 "2019-09-14T19:26:12Z")

</div>

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