# How come that my disk available on elasticsearch is stabilized while still ingesting data

**URL:** <https://discuss.elastic.co/t/how-come-that-my-disk-available-on-elasticsearch-is-stabilized-while-still-ingesting-data/216622>\
**Category:** Elasticsearch\
**Created:** [January 27, 2020, 9:01am UTC](https://discuss.elastic.co/t/how-come-that-my-disk-available-on-elasticsearch-is-stabilized-while-still-ingesting-data/216622 "2020-01-27T09:01:59Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Haalanam](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/haalanam/32/58782_2.png) [@Haalanam](https://discuss.elastic.co/u/Haalanam)\
**Post date:** [January 27, 2020, 9:01am UTC](https://discuss.elastic.co/t/how-come-that-my-disk-available-on-elasticsearch-is-stabilized-while-still-ingesting-data/216622/1 "2020-01-27T09:01:59Z")

</div>

Weird fact !  
I am ingesting data since now 10 days but my elasticsearch node is kind of stabilized to 94 %.  
What might causes that knowing that i dont delete any data.

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [January 27, 2020, 9:38am UTC](https://discuss.elastic.co/t/how-come-that-my-disk-available-on-elasticsearch-is-stabilized-while-still-ingesting-data/216622/2 "2020-01-27T09:38:27Z")

</div>

can you add some more context here? A single sentence problem statement rarely means, that the reader will understand everything.

Why is that problem? How should the system behave instead? What are your expectations? How did you check this? Is this a good or a bad sign? Are you adding more data during this time? What Elasticsearch version are you on?

---

<div class="post-metadata">

**Author:** ![Haalanam](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/haalanam/32/58782_2.png) [@Haalanam](https://discuss.elastic.co/u/Haalanam)\
**Post date:** [January 27, 2020, 11:34am UTC](https://discuss.elastic.co/t/how-come-that-my-disk-available-on-elasticsearch-is-stabilized-while-still-ingesting-data/216622/3 "2020-01-27T11:34:25Z")

</div>

Why is that problem?  
Not sure whether it's a problem or not.

How should the system behave instead?  
The available disk space should decrease while indexing over time.

What are your expectations?  
More data indexed should reduce the disk space

How did you check this?  
Via the stack Monitoring  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/3/d30f8c1d5114a6cf500e64f080370f9064316c5b.png)

Is this a good or a bad sign?  
I dont know

Are you adding more data during this time?  
yes

What Elasticsearch version are you on?  
Version 7.5.1

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [January 27, 2020, 2:39pm UTC](https://discuss.elastic.co/t/how-come-that-my-disk-available-on-elasticsearch-is-stabilized-while-still-ingesting-data/216622/4 "2020-01-27T14:39:51Z")

</div>

Have you checked that you are actually able to index data? Is the data indexed successful? I am asking because Elasticsearch uses a disk based shard allocator that stops allowing for writes at some point in time. See [https://www.elastic.co/guide/en/elasticsearch/reference/7.5/disk-allocator.html](https://www.elastic.co/guide/en/elasticsearch/reference/7.5/disk-allocator.html)

Can you share the output of a tried write operation?

---

<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:** [February 24, 2020, 2:41pm UTC](https://discuss.elastic.co/t/how-come-that-my-disk-available-on-elasticsearch-is-stabilized-while-still-ingesting-data/216622/5 "2020-02-24T14:41:18Z")

</div>

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