This section provides a list of common symptoms and possible actions that you can take to resolve issues when the master node becomes unhealthy or unavailable. This guide is particularly useful if you are not shipping your logs and metrics to a dedicated monitoring cluster.
What are the symptoms?
What is the impact?
- Only some search results are successful
- Ingesting, updating, and deleting data do not work
- Most Elasticsearch API requests fail
Some actions described here, such as stopping indexing or Machine Learning jobs, are temporary remediations intended to get your cluster into a state where you can make configuration changes to resolve the issue.
For production deployments, we recommend setting up a dedicated monitoring cluster to collect metrics and logs, troubleshooting views, and cluster alerts.
If your issue is not addressed here, open a topic in the Discuss forum or contact email@example.com.
Intro to Kibana
ELK for Logs & Metrics