What Do I Do If I Failed to Create an Index Pattern in an Elasticsearch Cluster?

Symptom

On the Dev Tools page of Kibana, run the GET .kibana/_settings command to query the Kibana index status. The value of the parameter read_only_allow_delete is true, which indicates that the cluster disk usage is too high.

Possible Cause

The index status is set to read-only.

Solution

1. Change the value of the parameter read_only_allow_delete to false and then create an index pattern.
2. Run the following command on the Dev Tools page of Kibana:

   PUT .kibana/_settings
   {
       "index": {
           "blocks": {
               "read_only_allow_delete": false
           }
       }
   }