Changing the disk.watermark thresholds for the Elasticsearch cluster.Changing the read_only setting for a specific index on an Elasticsearch cluster.Changing the read_only for a single index on an Elasticsearch cluster.Changing the read_only for all of indexes on an Elasticsearch cluster.Changing the read_only_allow_delete setting.Deleting specific Elasticsearch documents and indices to free up disk space.The forbidden 12 read only error Elasticsearch and the read delete only API error Elasticsearch can be addressed by: Remember, there are several options to correct these errors and you can use these strategies to stop getting the FORBIDDEN/12/index read-only / allow delete error. In this tutorial you learned how to address the FORBIDDEN Read-Only / Allow Delete Error for Elasticsearch API Requests. You can use the below _cat and _cluster APIs to get more information about your cluster: Increase the .watermark settings.Ĭlean up the indices and remove duplicates using a tool like Curator.ĭisable the _only_allow_delete setting. Some Solutions: Free up disk space on the hard drives that the cluster’s nodes are running on. If you get an index read-only / allow delete error, it may be because the free disk space on the hard drive the Elasticsearch cluster is running on is too low: Why Elasticsearch returns this error, and won’t allow PUT requests Elasticsearch will return a "Content-Type header" error if you omit the -H 'Content-Type: application/json' header option in a cURL request with a JSON body in the request: NOTE: All Elasticsearch versions 6.0 and newer will require a Content-Type header option anytime a cURL request is performed with a content body. This article will provide you with some tips to show you how to prevent this error from occurring. As Elasticsearch’s determination is based, by default, on the percentage of free disk space, this can occur on large disks even if you still have plenty of gigabytes of free disk space available. The forbidden 12 read only error Elasticsearch and the read delete only API error Elasticsearchx000D typically happens when Elasticsearch reads the disk as being low on storage space and will therefore put itself into “read-only” mode. When you execute an API request to make changes to a document or index on an Elasticsearch cluster you may sometimes receive a error that will block the request.
0 kommentar(er)
