Index Patterns Cannot Be Created for an Elasticsearch Cluster
Symptom
On the Dev Tools page of Kibana, run the GET .kibana/_settings command to query the status of the .kibana index. The value of the parameter read_only_allow_delete is true, which indicates that the cluster disk usage is too high.
Possible Cause
When the .kibana index becomes read-only, new index patterns cannot be created.
Solution
- Log in to Kibana.
- Log in to the CSS management console.
- In the navigation pane on the left, choose Clusters > Elasticsearch.
- In the cluster list, find the target cluster, and click Kibana in the Operation column to log in to the Kibana console.
- In the left navigation pane, choose Dev Tools.
- Run the following command to change the read_only_allow_delete parameter to false.
PUT .kibana/_settings { "index": { "blocks": { "read_only_allow_delete": false } } }
- Try creating new index patterns again.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot