{"id":2141,"date":"2022-10-11T07:30:33","date_gmt":"2022-10-11T07:30:33","guid":{"rendered":"https:\/\/meetanshi.com\/blog\/cluster-block-exception-in-magento-2\/"},"modified":"2026-04-22T15:43:44","modified_gmt":"2026-04-22T10:13:44","slug":"cluster-block-exception-in-magento-2","status":"publish","type":"post","link":"https:\/\/meetanshi.com\/blog\/cluster-block-exception-in-magento-2\/","title":{"rendered":"TOO_MANY_REQUESTS\/12\/disk usage exceeded flood-stage watermark, index has read-only-allow-delete block: Fix in Magento 2"},"content":{"rendered":"\n

Hello readers,<\/p>\n\n\n\n

I am back with a helpful solution to the ‘cluster block exception in Magento 2’ thrown by Elasticsearch.<\/p>\n\n\n\n

Recently, I stumbled upon an unforeseen error while reindexing in the Magento 2 (Adobe Commerce) store of one of my clients. In order to issue a reindex in Magento 2, I ran the following command:<\/p>\n\n\n\n

bin\/magento indexer:reindex<\/code><\/pre>\n\n\n\n
However, the result was unexpected. \ud83d\ude11<\/p>\n\n\n\n
The terminal threw the following error:<\/p>\n\n\n\n
Design Config Grid index has been rebuilt successfully in 00:00:00\nCustomer Grid index has been rebuilt successfully in 00:00:05\nCategory Flat Data index has been rebuilt successfully in 00:00:00\nCategory Products index has been rebuilt successfully in 00:00:06\nProduct Categories index has been rebuilt successfully in 00:00:00\nCatalog Rule Product index has been rebuilt successfully in 00:00:00\nProduct EAV index has been rebuilt successfully in 00:00:09\nStock index has been rebuilt successfully in 00:00:04\nInventory index has been rebuilt successfully in 00:00:00\nCatalog Product Rule index has been rebuilt successfully in 00:00:00\nProduct Price index has been rebuilt successfully in 00:01:57\nGoogle Product Removal Feed index has been rebuilt successfully in 00:00:00\nGoogle Product Feed index has been rebuilt successfully in 00:00:00\nCatalog Search index process unknown error:\n{\"error\":{\"root_cause\":[{\"type\":\"cluster_block_exception\",\"reason\":\"index [magento2_product_1_v1516] blocked by: [TOO_MANY_REQUESTS\/12\/disk usage exceeded flood-stage watermark, index has read-only-allow-delete block];\"}],\"type\":\"cluster_block_exception\",\"reason\":\"index [magento2_product_1_v1516] blocked by: [TOO_MANY_REQUESTS\/12\/disk usage exceeded flood-stage watermark, index has read-only-allow-delete block];\"},\"status\":429}<\/pre>\n\n\n\n
On further investigation, I came to know that ElasticSearch was the causative factor in the above case and was throwing the “cluster_block_exception” error due to low disk space. This error is thrown by ElasticSearch when the flood storage watermark level is exceeded. It puts ElasticSearch into a read-only mode.<\/p>\n\n\n\n
In this post, I will provide the step-wise solution to the ‘cluster block exception’ in Magento 2.<\/p>\n\n\n\n
Method to Solve ‘cluster block exception’ in Magento 2<\/h2>\n\n\n\n
The “disk usage exceeded flood-stage watermark” error while reindexing in Magento 2 can be solved by disabling the cluster routing allocation disk threshold. You can follow the steps mentioned below to solve the ‘cluster block exception’ in Magento 2<\/span>:<\/p>\n\n\n\n
Step 1:<\/strong> Run the following command in the root path of Magento 2:<\/p>\n\n\n\n
curl -XPUT -H \"Content-Type: application\/json\" http:\/\/localhost:9200\/_cluster\/settings -d '{ \"transient\": { \"cluster.routing.allocation.disk.threshold_enabled\": false } }'<\/code><\/pre>\n\n\n\n
Step 2:<\/strong> Try to perform reindexing again using the following command:<\/p>\n\n\n\n
curl -XPUT -H \"Content-Type: application\/json\" http:\/\/localhost:9200\/_all\/_settings -d '{\"index.blocks.read_only_allow_delete\": null}'<\/code><\/pre>\n\n\n\n
That’s it!<\/p>\n\n\n\n
Magento 2 (Adobe Commerce) will perform the reindexing normally again! \ud83d\ude80<\/p>\n\n\n\n
You can also use the programmatic method to perform reindexing in Magento 2<\/a> after solving the issue using this solution.<\/p>\n\n\n\n
In case you are still facing any issues or have any queries regarding the provided solution, please feel free to comment. Also, do not forget to share this solution with your Magento friends via social media. \ud83d\ude07<\/p>\n\n\n\n
Thanks for reading. \ud83c\udf40<\/p>\n","protected":false},"excerpt":{"rendered":"
Hello readers, I am back with a helpful solution to the ‘cluster block exception in Magento 2’ thrown by Elasticsearch. Recently, I stumbled upon an…<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[34],"tags":[],"class_list":["post-2141","post","type-post","status-publish","format-standard","hentry","category-magento"],"acf":[],"_links":{"self":[{"href":"https:\/\/meetanshi.com\/blog\/wp-json\/wp\/v2\/posts\/2141","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/meetanshi.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/meetanshi.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/meetanshi.com\/blog\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/meetanshi.com\/blog\/wp-json\/wp\/v2\/comments?post=2141"}],"version-history":[{"count":3,"href":"https:\/\/meetanshi.com\/blog\/wp-json\/wp\/v2\/posts\/2141\/revisions"}],"predecessor-version":[{"id":26366,"href":"https:\/\/meetanshi.com\/blog\/wp-json\/wp\/v2\/posts\/2141\/revisions\/26366"}],"wp:attachment":[{"href":"https:\/\/meetanshi.com\/blog\/wp-json\/wp\/v2\/media?parent=2141"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/meetanshi.com\/blog\/wp-json\/wp\/v2\/categories?post=2141"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/meetanshi.com\/blog\/wp-json\/wp\/v2\/tags?post=2141"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}