Catalogue is in read-only mode
The latest version of the archive admin console indicates if your catalogue is in read-only mode.
If you run the harvester when the catalogue is in read-only mode then you will see the following errors in the log-files of the archive.
[0]: index [metadatafiles], type [search], id [ovl0nH8BF4WRu26gnjcI], message [ElasticsearchException[Elasticsearch exception [type=cluster_block_exception, reason=blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];]]]
[1]: index [simulatedmetadata_seamless], type [seamless_integration_search], id [o_l0nH8BF4WRu26gnjcI], message [ElasticsearchException[Elasticsearch exception [type=cluster_block_exception, reason=blocked by: [FORBIDDEN/12/index read-only / allow delete
...
(api)];]]]
If the catalogue is in When you see these types of errors in your log-files then elastic has switched to read-only mode . This will cause that then the catalogue can no longer be updated. Elastic will switch to read-only mode when the available disk-space is less then 5%. Note that elastic will stay in read-only mode even when you make more disk space available.
...