# Elasticsearch does not use all path.data **URL:** \ **Category:** Elasticsearch\ **Created:** [April 20, 2020, 4:45pm UTC](https://discuss.elastic.co/t/elasticsearch-does-not-use-all-path-data/228905 "2020-04-20T16:45:04Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![mobidyc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mobidyc/32/42027_2.png) [@mobidyc](https://discuss.elastic.co/u/mobidyc)\ **Post date:** [April 20, 2020, 4:45pm UTC](https://discuss.elastic.co/t/elasticsearch-does-not-use-all-path-data/228905/1 "2020-04-20T16:45:05Z")
Good morning guys, I setup multiple path.data but when I check the disk usage, the repartition seems wrong. ```auto [root@cld0286su ssd9]# grep path.data /etc/elasticsearch/elasticsearch.yml path.data: /srv/ssd1/elasticsearch,/srv/ssd2/elasticsearch,/srv/ssd3/elasticsearch,/srv/ssd4/elasticsearch,/srv/ssd5/elasticsearch,/srv/ssd6/elasticsearch,/srv/ssd7/elasticsearch,/srv/ssd8/elasticsearch,/srv/ssd9/elasticsearch [root@cld0286su ssd9]# du -hs /srv/ssd*/elasticsearch/ 664K /srv/ssd1/elasticsearch/ 664K /srv/ssd2/elasticsearch/ 664K /srv/ssd3/elasticsearch/ 4,6G /srv/ssd4/elasticsearch/ 664K /srv/ssd5/elasticsearch/ 664K /srv/ssd6/elasticsearch/ 780K /srv/ssd7/elasticsearch/ 664K /srv/ssd8/elasticsearch/ 56G /srv/ssd9/elasticsearch/ [root@cld0286su ssd9]# ``` Of course I checked the number of shards (and size) to be sure the everything does not belong to the same shard ```auto [root@cld0286su ssd9]# curl -s 127.0.0.1:9200/_cat/shards |grep cld0286su |wc -l 48 [root@cld0286su ssd9]# [root@cld0286su ssd9]# curl -s 127.0.0.1:9200/_cat/shards |grep cld0286su |grep gb stats-disk-2020.04-archive 0 r STARTED 7956473 1.5gb 10.160.186.91 cld0286su stats-disk-2019.11-archive 4 p STARTED 22652670 4.5gb 10.160.186.91 cld0286su stats-disk-2020.04.11 3 r STARTED 24827005 4.9gb 10.160.186.91 cld0286su stats-disk-2020.04.18 0 p STARTED 24328432 4.9gb 10.160.186.91 cld0286su stats-disk-2020.04.06 2 r STARTED 25472127 5.2gb 10.160.186.91 cld0286su stats-disk-2019.12-archive 3 r STARTED 23155079 4.7gb 10.160.186.91 cld0286su stats-disk-2020.03-archive 2 r STARTED 25373517 5.1gb 10.160.186.91 cld0286su stats-disk-2019.10-archive 11 r STARTED 23814628 4.7gb 10.160.186.91 cld0286su stats-disk-2020.04.15 0 p STARTED 25351113 5.1gb 10.160.186.91 cld0286su stats-disk-2019.08-archive 7 r STARTED 23253432 4.7gb 10.160.186.91 cld0286su stats-disk-2020.01-archive 8 p STARTED 23153243 4.6gb 10.160.186.91 cld0286su stats-disk-2020.02-archive 5 r STARTED 22064042 4.3gb 10.160.186.91 cld0286su [root@cld0286su ssd9]# [root@cld0286su ssd9]# df -h ../ssd* Filesystem Size Used Avail Use% Mounted on /dev/sdak 184G 130G 54G 71% /srv/ssd1 /dev/sdal 184G 161G 23G 88% /srv/ssd2 /dev/sdam 184G 142G 42G 78% /srv/ssd3 /dev/sdan 184G 108G 76G 59% /srv/ssd4 /dev/sdao 184G 127G 57G 70% /srv/ssd5 /dev/sdap 184G 130G 54G 71% /srv/ssd6 /dev/sdaq 184G 113G 71G 62% /srv/ssd7 /dev/sdar 184G 120G 65G 65% /srv/ssd8 /dev/sdbg 373G 156G 218G 42% /srv/ssd9 [root@cld0286su ssd9]# ``` Configuration is the following: ```auto [root@cld0286su ssd9]# cat /etc/elasticsearch/elasticsearch.yml bootstrap.system_call_filter: false # requires kernel 3.5+ with CONFIG_SECCOMP and CONFIG_SECCOMP_FILTER compiled in cluster.name: MyCluster cluster.routing.allocation.disk.watermark.flood_stage: "99%" cluster.routing.allocation.disk.watermark.high: "94%" cluster.routing.allocation.disk.watermark.low: "90%" discovery.zen.minimum_master_nodes: 26 discovery.zen.ping.unicast.hosts: ['xxx'] http.cors.allow-origin: "*" http.cors.enabled: true network.bind_host: ['xxx'] network.publish_host: 10.160.186.91 node.data: True node.master: False node.name: cld0286su path.data: /srv/ssd1/elasticsearch,/srv/ssd2/elasticsearch,/srv/ssd3/elasticsearch,/srv/ssd4/elasticsearch,/srv/ssd5/elasticsearch,/srv/ssd6/elasticsearch,/srv/ssd7/elasticsearch,/srv/ssd8/elasticsearch,/srv/ssd9/elasticsearch path.logs: /data/logs/elasticsearch/ reindex.remote.whitelist: "*:9200, *:9201" xpack.security.enabled: false xpack.monitoring.enabled: true xpack.monitoring.elasticsearch.collection.enabled: true discovery.zen.fd.ping_interval: 1s discovery.zen.fd.ping_timeout: 2s discovery.zen.fd.ping_retries: 3 [root@cld0286su ssd9]# ``` I do not see what could be wrong in the disk allocator configuration, cluster is stable and almost never has relocations. Is there a way to move shards to a specific disk? Maybe by stopping the node, moving the shard folder and restart the service (but it would be a pain as I have around 50 servers in the same situation) ? Any help appreciated 😉 ---
**Author:** ![willemdh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/willemdh/32/16922_2.png) [@willemdh](https://discuss.elastic.co/u/willemdh)\ **Post date:** [April 21, 2020, 6:06am UTC](https://discuss.elastic.co/t/elasticsearch-does-not-use-all-path-data/228905/2 "2020-04-21T06:06:16Z")
Maybe try data path as array: ``` path: data: - /mnt/elasticsearch_1 - /mnt/elasticsearch_2 - /mnt/elasticsearch_3 ``` ---
**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:** [April 21, 2020, 6:24am UTC](https://discuss.elastic.co/t/elasticsearch-does-not-use-all-path-data/228905/3 "2020-04-21T06:24:19Z")
++ to that, it's how the docs reference it - [https://www.elastic.co/guide/en/elasticsearch/reference/7.6/path-settings.html](https://www.elastic.co/guide/en/elasticsearch/reference/7.6/path-settings.html) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 19, 2020, 6:24am UTC](https://discuss.elastic.co/t/elasticsearch-does-not-use-all-path-data/228905/4 "2020-05-19T06:24:22Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.