observing error in elasticsearch logs as : ClusterBlockException: index [.ds-.logs-deprecation.elasticsearch-default-2022.10.27-000023] blocked by: [TOO_MANY_REQUESTS/12/disk usage exceeded flood-stage watermark, index has read-only-allow-delete block];

observing error in elasticsearch logs as : ClusterBlockException: index [.ds-.logs-deprecation.elasticsearch-default-2022.10.27-000023] blocked by: [TOO_MANY_REQUESTS/12/disk usage exceeded flood-stage watermark, index has read-only-allow-delete block];

Hi Vandana, this is likely being caused by Elasticsearch thinking that the disk is running low on space. Elasticsearch enters read-only mode when it perceives low disk space, triggered by the default flood stage watermark set at 95%. This means even with many gigabytes of free space on large disks, the system can still activate the read-only mode. For instance, a 1TB drive requires at least 50GB of free space to avoid read-only mode activation.

I'm not sure what version of the stack you're running, but here are the latest docs on disk allocation management that may be helpful for you.

The solution to this problem may be to free up disk space until more than 5% is available, or to change the flood stage watermark settings (details are in the docs link above).

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