# Mixing ssd and hdd in path.data is not working

**URL:** <https://discuss.elastic.co/t/mixing-ssd-and-hdd-in-path-data-is-not-working/99180>\
**Category:** Elasticsearch\
**Created:** [September 2, 2017, 12:50am UTC](https://discuss.elastic.co/t/mixing-ssd-and-hdd-in-path-data-is-not-working/99180 "2017-09-02T00:50:42Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![elasticuser1](https://avatars.discourse-cdn.com/v4/letter/e/a3d4f5/32.png) [@elasticuser1](https://discuss.elastic.co/u/elasticuser1)\
**Post date:** [September 2, 2017, 12:50am UTC](https://discuss.elastic.co/t/mixing-ssd-and-hdd-in-path-data-is-not-working/99180/1 "2017-09-02T00:50:43Z")

</div>

Hi,

For one of ES instances, we pointed path.data to both hdd and ssd.

path.data: /dir/d05/elasticsearch/data,/ssd/elasticsearch/data

This setup is not working. I found there is NO data being written to ssd except \_state.

Is this wrong setup? Has any one experienced this issue before?

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago)\
**Post date:** [September 2, 2017, 2:35am UTC](https://discuss.elastic.co/t/mixing-ssd-and-hdd-in-path-data-is-not-working/99180/2 "2017-09-02T02:35:28Z")

</div>

Please, post the output of:

```auto
GET _cat/shards?v

```

---

<div class="post-metadata">

**Author:** ![elasticuser1](https://avatars.discourse-cdn.com/v4/letter/e/a3d4f5/32.png) [@elasticuser1](https://discuss.elastic.co/u/elasticuser1)\
**Post date:** [September 2, 2017, 3:49am UTC](https://discuss.elastic.co/t/mixing-ssd-and-hdd-in-path-data-is-not-working/99180/3 "2017-09-02T03:49:13Z")

</div>

Thanks @thiago. This is sensitive data. Please suggest what should I look at specifically.

---

<div class="post-metadata">

**Author:** ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago)\
**Post date:** [September 2, 2017, 3:51am UTC](https://discuss.elastic.co/t/mixing-ssd-and-hdd-in-path-data-is-not-working/99180/4 "2017-09-02T03:51:24Z")

</div>

Sensitive? It's just a bunch of index names... 😄

Anyway, how many nodes and how many shards you have?

---

<div class="post-metadata">

**Author:** ![elasticuser1](https://avatars.discourse-cdn.com/v4/letter/e/a3d4f5/32.png) [@elasticuser1](https://discuss.elastic.co/u/elasticuser1)\
**Post date:** [September 2, 2017, 4:18am UTC](https://discuss.elastic.co/t/mixing-ssd-and-hdd-in-path-data-is-not-working/99180/5 "2017-09-02T04:18:20Z")

</div>

4 data nodes with 3 instances on each. We have 916 shards.

---

<div class="post-metadata">

**Author:** ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago)\
**Post date:** [September 2, 2017, 4:21am UTC](https://discuss.elastic.co/t/mixing-ssd-and-hdd-in-path-data-is-not-working/99180/6 "2017-09-02T04:21:06Z")

</div>

After you have added this extra path configured, were any index created?

---

<div class="post-metadata">

**Author:** ![elasticuser1](https://avatars.discourse-cdn.com/v4/letter/e/a3d4f5/32.png) [@elasticuser1](https://discuss.elastic.co/u/elasticuser1)\
**Post date:** [September 2, 2017, 4:33am UTC](https://discuss.elastic.co/t/mixing-ssd-and-hdd-in-path-data-is-not-working/99180/7 "2017-09-02T04:33:29Z")

</div>

Yes @thiago

---

<div class="post-metadata">

**Author:** ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago)\
**Post date:** [September 2, 2017, 4:47am UTC](https://discuss.elastic.co/t/mixing-ssd-and-hdd-in-path-data-is-not-working/99180/8 "2017-09-02T04:47:23Z")

</div>

Ok. So what I can tell you now is that when you configure a new data path, Elasticsearch won't start moving existing shards to it. Only when newly created indices in which shards are assigned to that node is that Elasticsearch will create shards on the new data path. So if you are creating daily indices with just one shard, for instance, it might take a few days until that data path actually gets selected.

---

<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 30, 2017, 4:47am UTC](https://discuss.elastic.co/t/mixing-ssd-and-hdd-in-path-data-is-not-working/99180/9 "2017-09-30T04:47:25Z")

</div>

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