What Should I Do When Elasticsearch Runs into Read-only Mode?

When Tamr is running out of disk space performing an operation that involves Elasticsearch, you may experience slow UI and be presented with one of the following error messages:

"UnifyElasticSearchDataCluster":{"healthy":false,"message":"Cluster Status: GREEN but the following indexes are in read-only mode: [tamr_project_x, tamr_project_x1]. This might be caused by high disk usage.
ClusterBlockException[blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];]

To resolve this issue, have a look at our public docs and try implementing the suggested steps. If this does not work, reach out to [email protected] for further assistance.


Did this page help you?