This can happen if you are nearly out of disk space. If you have used 95% or more of your disk, Elasticsearch enforces a read-only index (no index. This means no update and adding to the index is allowed only deletion will work).work. **You just have to clean up your disk to have more than 5% free disk space (anyway a good idea) idea:) and restart Axon.ivy and Axon.ivy. Then it should work again.** See detailed information in the [Elasticsearch reference][1] about the configuration properties and what happens when. [1]: https://www.elastic.co/guide/en/elasticsearch/reference/current/disk-allocator.html

This can happen if you have low are nearly out of disk space. If you have used 95% or more of your disk space, disk, Elasticsearch enforces a read-only index (no update and adding to the index is allowed only deletion will work). **You just have to clean up your disk to have more than 5% free disk space (anyway a good idea) and restart Axon.ivy and it should work again.** See detailed information in the [Elasticsearch reference][1] about the configuration properties and what happens when. [1]: https://www.elastic.co/guide/en/elasticsearch/reference/current/disk-allocator.html

This can happen if you have low disk space. If you have used 95% or more of your disk space, Elasticsearch enforces a read-only index (no update and adding to the index is allowed only deletion will work). You **You just have to clean up your disk to have more than 5% free disk space (anyway a good idea) and restart Axon.ivy and it should work again.again.** See detailed information in the [Elasticsearch reference][1] about the configuration properties and what happens when. [1]: https://www.elastic.co/guide/en/elasticsearch/reference/current/disk-allocator.html

This happens normally can happen if you have low disk space. If you have used 95% or more of your disk space, Elasticsearch enforces a read-only index (no update and adding to the index is allowed only deletion).deletion will work). You just have to clean up your disk to have more than 5% free disk space (anyway a good idea) and restart Axon.ivy and it should work again. See detailed information in the [Elasticsearch reference][1].reference][1] about the configuration properties and what happens when. [1]: https://www.elastic.co/guide/en/elasticsearch/reference/current/disk-allocator.html

This happens normally if you have low disk space. If you have used 95% or more of your disk space, Elasticsearch enforces a read-only index (only deletion (no update and adding to the index is allowed).allowed only deletion). You just have to clean up your disk to have more than 5% free disk space and restart Axon.ivy and it should work again. See detailed information in the [Elasticsearch reference][1]. [1]: https://www.elastic.co/guide/en/elasticsearch/reference/current/disk-allocator.html

This happens normally if you have low disk space. If you have used 95% or more of your disk space, Elasticsearch enforces a read-only index (only deletion is allowed). See detailed information in the [ElasitSearch docu][1].[Elasticsearch reference][1]. [1]: https://www.elastic.co/guide/en/elasticsearch/reference/current/disk-allocator.html

This happens normally if you have low disk space. If you have used 95% or more of your disk space, Elasticsearch enforces a read-only index (only deletion is allowed). See detailed information in the [ElasitSearch docu][1]. [1]: https://www.elastic.co/guide/en/elasticsearch/reference/current/disk-allocator.html

This happens normally if you have low disk space. If you have used 95% of your disk space, Elasticsearch enforces a read-only index (only deletion is allowed). See detailed information in the [ElasitSearch docu][1]. [1]: https://www.elastic.co/guide/en/elasticsearch/reference/current/disk-allocator.html