When configured correctly, Elasticsearch clusters are highly available and fault tolerant. That doesn’t necessarily mean they are impervious to failure. Human error and hardware failure are always a possibility. Troubleshooting data availability issues on a distributed system can be a challenge. In this hands-on lab, we will use the cluster allocation explain API to demystify the troubleshooting process of shard allocation issues in Elasticsearch.
Learning Objectives
Successfully complete this lab by achieving the following learning objectives:
- Troubleshoot any red-state indices.
Using the Secure Shell (SSH), log in to the data-1
node ascloud_user` via the public IP address.Start the elasticsearch node with:
sudo systemctl start elasticsearchUse the Kibana console tool to execute the following:
PUT logs-02/_settings { "number_of_replicas": 1 }- Troubleshoot any yellow-state indices.
Use the Kibana console tool to execute the following:
PUT logs-01/_settings { "number_of_replicas": 1 }
