# Increase disk allocation for Elastic Search on linux

**URL:** <https://discuss.elastic.co/t/increase-disk-allocation-for-elastic-search-on-linux/242470>\
**Category:** Elasticsearch\
**Created:** [July 24, 2020, 7:37am UTC](https://discuss.elastic.co/t/increase-disk-allocation-for-elastic-search-on-linux/242470 "2020-07-24T07:37:04Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rao7806](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rao7806/32/48333_2.png) [@rao7806](https://discuss.elastic.co/u/rao7806)\
**Post date:** [July 24, 2020, 7:37am UTC](https://discuss.elastic.co/t/increase-disk-allocation-for-elastic-search-on-linux/242470/1 "2020-07-24T07:37:04Z")

</div>

We are trying to index large datasets to elastic search and indexing is stopped due to watermark reached and nodes are set to read-only.

We ran the command

```auto
GET /_cat/allocation?v

```

and from the output, we came to know that the disk space allocated for elastic is 10Gb and 95% is occupied. We have some more free space on our machine that can be allocated to elastic.

We are trying to figure out how to increase the space allocation to elastic search. Any pointers would be helpful.

---

<div class="post-metadata">

**Author:** ![Steve\_Mushero](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steve_mushero/32/22441_2.png) [@Steve\_Mushero](https://discuss.elastic.co/u/Steve_Mushero)\
**Post date:** [July 24, 2020, 8:10am UTC](https://discuss.elastic.co/t/increase-disk-allocation-for-elastic-search-on-linux/242470/2 "2020-07-24T08:10:57Z")

</div>

This really depends on your Linux setup and the file systems in use, the cloud or drives in use, etc. Having only 10GB is very small, but maybe some default root file system was setup that way - typically you'd see very large (like 1TB+) root disks or a 2nd mounted disk like that, mounted for the ES data directory - but these are no really Elasticsearch questions; all about Linux storage.

---

<div class="post-metadata">

**Author:** ![rao7806](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rao7806/32/48333_2.png) [@rao7806](https://discuss.elastic.co/u/rao7806)\
**Post date:** [July 24, 2020, 9:43am UTC](https://discuss.elastic.co/t/increase-disk-allocation-for-elastic-search-on-linux/242470/3 "2020-07-24T09:43:04Z")

</div>

We do have space on the disk available... we tried running free -g command and we see around 15gb available... We are unable to figure out how to tell elastic to use that sounds trivial but we are trying to understand where elastic search saves data and how to how it calculates the available space and is trying to tell Elastic Search to use the space available instead of restricting itself to 10GB

---

<div class="post-metadata">

**Author:** ![Steve\_Mushero](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steve_mushero/32/22441_2.png) [@Steve\_Mushero](https://discuss.elastic.co/u/Steve_Mushero)\
**Post date:** [July 24, 2020, 10:00am UTC](https://discuss.elastic.co/t/increase-disk-allocation-for-elastic-search-on-linux/242470/4 "2020-07-24T10:00:19Z")

</div>

You can see in the config where it stores the data, such as /var/lib/elasticsearch or /var/lib/elasticsearch/data

Your node stats will show you, such as: GET /\_nodes/stats, which for a cluster I'm looking at shows:  
"data" : [  
{  
"path" : "/var/lib/elasticsearch/nodes/0",  
"mount" : "/var/lib/elasticsearch (/dev/nvme1n1p1)",  
"type" : "xfs",  
"total\_in\_bytes" : 1073216491520,  
"free\_in\_bytes" : 432963375104,  
"available\_in\_bytes" : 432963375104

What is your 'df -h ' output? You can then see your mounted file systems, space, etc.

---

<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:** [August 21, 2020, 10:00am UTC](https://discuss.elastic.co/t/increase-disk-allocation-for-elastic-search-on-linux/242470/5 "2020-08-21T10:00:23Z")

</div>

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