# Getting cluster\_block\_exception Root causes when both memory and diskspace is plenty

**URL:** <https://discuss.elastic.co/t/getting-cluster-block-exception-root-causes-when-both-memory-and-diskspace-is-plenty/351311>\
**Category:** Elastic Search\
**Tags:** elastic-app-search\
**Created:** [January 17, 2024, 9:50pm UTC](https://discuss.elastic.co/t/getting-cluster-block-exception-root-causes-when-both-memory-and-diskspace-is-plenty/351311 "2024-01-17T21:50:54Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Keith\_Lin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/keith_lin/32/130566_2.png) [@Keith\_Lin](https://discuss.elastic.co/u/Keith_Lin)\
**Post date:** [January 17, 2024, 9:50pm UTC](https://discuss.elastic.co/t/getting-cluster-block-exception-root-causes-when-both-memory-and-diskspace-is-plenty/351311/1 "2024-01-17T21:50:54Z")

</div>

I'm getting the following error when trying to create an alert rule in kibana

```auto
[.kibana_alerting_cases_8.8.2_001] blocked by: [FORBIDDEN/8/index write (api)];: cluster_block_exception Root causes: cluster_block_exception: index [.kibana_alerting_cases_8.8.2_001] blocked by: [FORBIDDEN/8/index write (api)];

```

My cluster seems very healthy with lots of memory and disk space. Can anyone give me some pointers on how to solve it?

 ![Screenshot 2024-01-17 at 4.48.55 PM](https://us1.discourse-cdn.com/elastic/original/3X/0/6/061ec19f02c07636388005c9a63623cf34fbde00.png)

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [January 21, 2024, 8:02pm UTC](https://discuss.elastic.co/t/getting-cluster-block-exception-root-causes-when-both-memory-and-diskspace-is-plenty/351311/2 "2024-01-21T20:02:39Z")

</div>

> [@Keith\_Lin](#):
>
> `FORBIDDEN/8/index write`

What is the full output of the [cluster stats API](https://www.elastic.co/guide/en/elasticsearch/reference/8.12/cluster-stats.html)?

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [January 21, 2024, 11:20pm UTC](https://discuss.elastic.co/t/getting-cluster-block-exception-root-causes-when-both-memory-and-diskspace-is-plenty/351311/3 "2024-01-21T23:20:24Z")

</div>

> [@Keith\_Lin](#):
>
> My cluster seems very healthy with lots of memory and disk space.

You need to check the disk space available per node, the monitoring overview page will show you the disk space available for the entire cluster, but you may have some node where the disk is full and other where the disk still has space.

You may have some nodes that reached the flood watermark, which will block write request to the indices that have at least one shard on that node.

---

<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 18, 2024, 11:20pm UTC](https://discuss.elastic.co/t/getting-cluster-block-exception-root-causes-when-both-memory-and-diskspace-is-plenty/351311/4 "2024-02-18T23:20:52Z")

</div>

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