# Unable to login when disk is full

**URL:** https://discuss.elastic.co/t/unable-to-login-when-disk-is-full/257314
**Category:** Kibana
**Created:** [December 2, 2020, 7:27am UTC](https://discuss.elastic.co/t/unable-to-login-when-disk-is-full/257314 "2020-12-02T07:27:52Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![hazcod](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hazcod/32/67689_2.png) [@hazcod](https://discuss.elastic.co/u/hazcod)
#### Post date: [December 2, 2020, 7:27am UTC](https://discuss.elastic.co/t/unable-to-login-when-disk-is-full/257314/1 "2020-12-02T07:27:53Z")

</div>

Hi,

I am unable to login into Kibana when my elasticsearch cluster is getting full.  
The log will contain:

```auto
org.elasticsearch.xpack.monitoring.exporter.ExportException: CLusterBlockException: blocked by: [TOO_MANY_REQUESTS/12/disk usage exceeded flood-stage watermark, index has read-only-allow-delete-block]

```

Altough my elasticsearch volume still has 2.9GB of 35GB available.  
Any idea what I should do?

---

<div class="post-metadata">

### Author: ![matw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/matw/32/13913_2.png) [@matw](https://discuss.elastic.co/u/matw)
#### Post date: [December 2, 2020, 7:37am UTC](https://discuss.elastic.co/t/unable-to-login-when-disk-is-full/257314/2 "2020-12-02T07:37:53Z")

</div>

Hi

When Elasticsearch is running out of disk space, there's a configurable limit when indices are set to read only( `cluster.routing.allocation.disk.watermark.flood_stage`) . This is the reason why you can no longer login into Kibana. You would need to reconfigure those flood stages, here is an explanation:

> **[Cluster-level shard allocation and routing settings | Elasticsearch Reference...](https://www.elastic.co/guide/en/elasticsearch/reference/master/modules-cluster.html#disk-based-shard-allocation)**

Best,  
Matthias

---

<div class="post-metadata">

### Author: ![hazcod](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hazcod/32/67689_2.png) [@hazcod](https://discuss.elastic.co/u/hazcod)
#### Post date: [December 2, 2020, 11:00am UTC](https://discuss.elastic.co/t/unable-to-login-when-disk-is-full/257314/3 "2020-12-02T11:00:40Z")

</div>

Hi @matw, but since login is readonly, I don't understand with login would disabled?  
The cluster is practically unuseable web-wise if the storage gets full, which turns into a Denial-of-Service vulnerability if you're running something important such as a SIEM.

Thanks!

---

<div class="post-metadata">

### Author: ![matw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/matw/32/13913_2.png) [@matw](https://discuss.elastic.co/u/matw)
#### Post date: [December 3, 2020, 12:40pm UTC](https://discuss.elastic.co/t/unable-to-login-when-disk-is-full/257314/4 "2020-12-03T12:40:10Z")

</div>

Kibana stores data in `.kibana` prefixed indices, and before 7.10 login was not always read-only, and in 7.10+ it's never read-only (we create session).

Generally could try to reset readonly setting by

```
PUT /indexname/_settings
{
  "index.blocks.read_only_allow_delete": null
}

```

What error message is displayed when you try to login in the flooded state?

Thx & Best;  
Matthias

---

<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: [December 31, 2020, 12:40pm UTC](https://discuss.elastic.co/t/unable-to-login-when-disk-is-full/257314/5 "2020-12-31T12:40:18Z")

</div>

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