# Elasticsearch node is at 100% disk usage, unable to edit configuration

**URL:** https://discuss.elastic.co/t/elasticsearch-node-is-at-100-disk-usage-unable-to-edit-configuration/351017
**Category:** Elastic Cloud Enterprise (ECE)
**Created:** [January 13, 2024, 9:56pm UTC](https://discuss.elastic.co/t/elasticsearch-node-is-at-100-disk-usage-unable-to-edit-configuration/351017 "2024-01-13T21:56:35Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![Sanskar\_Panchal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sanskar_panchal/32/127394_2.png) [@Sanskar\_Panchal](https://discuss.elastic.co/u/Sanskar_Panchal)
#### Post date: [January 13, 2024, 9:56pm UTC](https://discuss.elastic.co/t/elasticsearch-node-is-at-100-disk-usage-unable-to-edit-configuration/351017/1 "2024-01-13T21:56:35Z")

</div>

Hi,

One of my Elasticsearch instance is at 100% disk usage.

Which has resulted into NODE\_LEFT.  
Which then caused " This cluster has 39 unavailable primaries, 101 unavailable replicas."

And cluster is now at red health status.

I tried increasing disk size per zone , but any configuration change is not applied. (maybe because of red cluster health)

I tried deleting some non useful indices in hot\_tier and also reduced no. of replicas for some indices for nothing seems reduce space in the full node.

The full disk node is also not visible when \_cat/nodes is run:

```auto
GET _cat/nodes?h=id,name,r,u,du

OUTPUT:
nggi instance-0000000022 himrst 110.3d 68.1gb
Xy2c instance-0000000023 rw 93.6d 237.8gb
BoE0 instance-0000000024 cr 82.5d 27.5mb
jfxF tiebreaker-0000000017 mv 156.2d 24mb
BvYm instance-0000000016 rw 177.7d 237.8gb

```

 ![nodes](https://us1.discourse-cdn.com/elastic/original/3X/4/c/4c56793e996aa8c4f7e812bc0538a051f2517c5a.png)

How can I resolve this ?

---

<div class="post-metadata">

### Author: ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)
#### Post date: [January 14, 2024, 2:17am UTC](https://discuss.elastic.co/t/elasticsearch-node-is-at-100-disk-usage-unable-to-edit-configuration/351017/2 "2024-01-14T02:17:14Z")

</div>

@Sanskar_Panchal

You should open a support ticket through Elastic Support.

---

<div class="post-metadata">

### Author: ![Sanskar\_Panchal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sanskar_panchal/32/127394_2.png) [@Sanskar\_Panchal](https://discuss.elastic.co/u/Sanskar_Panchal)
#### Post date: [January 14, 2024, 6:59am UTC](https://discuss.elastic.co/t/elasticsearch-node-is-at-100-disk-usage-unable-to-edit-configuration/351017/3 "2024-01-14T06:59:22Z")

</div>

Actually i don't have the required subscribtion level to open a case in elastic support.  
That button is greyed out for me.

---

<div class="post-metadata">

### Author: ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)
#### Post date: [January 14, 2024, 7:24am UTC](https://discuss.elastic.co/t/elasticsearch-node-is-at-100-disk-usage-unable-to-edit-configuration/351017/4 "2024-01-14T07:24:38Z")

</div>

Exactly what product are you using?

Elastic Cloud?

[cloud.elastic.co](http://cloud.elastic.co)?

---

<div class="post-metadata">

### Author: ![Sanskar\_Panchal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sanskar_panchal/32/127394_2.png) [@Sanskar\_Panchal](https://discuss.elastic.co/u/Sanskar_Panchal)
#### Post date: [January 14, 2024, 7:52am UTC](https://discuss.elastic.co/t/elasticsearch-node-is-at-100-disk-usage-unable-to-edit-configuration/351017/5 "2024-01-14T07:52:03Z")

</div>

Yes , I am using [https://cloud.elastic.co](https://cloud.elastic.co) and I am at Standard subscription level.

 ![Screenshot_20240114-132135-973](https://us1.discourse-cdn.com/elastic/original/3X/7/6/76c2687772a8c50a4fa2797ee781d9478b1e1612.png)

---

<div class="post-metadata">

### Author: ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)
#### Post date: [January 14, 2024, 4:18pm UTC](https://discuss.elastic.co/t/elasticsearch-node-is-at-100-disk-usage-unable-to-edit-configuration/351017/6 "2024-01-14T16:18:45Z")

</div>

> **[Official Elasticsearch Pricing: Elastic Cloud, Managed Elasticsearch](https://www.elastic.co/pricing)**
>
> Get started with our managed Elasticsearch Service on your choice of AWS, Azure, or Google Cloud platforms. Download the Elastic Stack for private and hybrid cloud. Start with a free 14-day trial and ...

Someone in your org has support Support comes with Standard see page and below.

Standard  
SUPPORT  
Web-based support  
2 Support Contacts  
3-business day target response time (Elastic Cloud only)

Anyway

Try to set the bad node to Stop Routing it in the 3 little dots.

Then try to scale nodes to 8 GB

Or if stopped routing already try to start routing and delete indices.

See if that will work.

But finding who has your support contact and filing ticket is probably Best

---

<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: [January 28, 2024, 4:18pm UTC](https://discuss.elastic.co/t/elasticsearch-node-is-at-100-disk-usage-unable-to-edit-configuration/351017/7 "2024-01-28T16:18:59Z")

</div>

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