[cluster_block_exception] - Disk allocation and usage help!

[rickwest]

Morning all,

New Elasticsearch user here and trying to integrate it into a project that I'm working on. Currently just working locally with Elasticsearch using Ubuntu 18.04.

I have been working for the past week or so, creating indexes, indexing documents, searching and just generally getting familiar with things.

However, I have now hit a problem:

[cluster_block_exception] blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];

it appears that my index is being forced into read-only mode due to 95% of disk space being used.

However, I don't understand this or know how to rectify it, I have deleted all my indexes bar the 4kb .kibana index so I don't understand the used disk space?

Would really love it if anyone can shed some light on this, i'm stuck, and please forgive my ignorance!

Much appreciated,

Rick

[DavidTurner]

Hi @rickwest and welcome!

Here's a link to the docs on disk-based shard allocation, which tells you how to remove the read-only block once you've freed up the space:

An example of resetting the read-only index block on the twitter index:

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