Why cluster health ensures reliability in Elasticsearch

Introduction

Cluster health shows if all parts of your Elasticsearch system are working well together. It helps keep your data safe and your search fast.

When you want to check if your Elasticsearch system is ready to handle searches.

Before adding or removing nodes to make sure the system stays stable.

To find out if any part of your cluster is having problems that could cause data loss.

When monitoring system status to avoid downtime.

Before running big data operations to ensure the cluster can handle the load.

Syntax

Elasticsearch

GET /_cluster/health

Response example:
{
  "cluster_name": "my_cluster",
  "status": "green",  // can be green, yellow, or red
  "number_of_nodes": 3,
  "active_shards": 10
}

The status field shows the health: green means all is good, yellow means some replicas are not assigned but data is safe, red means some data is missing or unavailable.

You use the GET /_cluster/health API to check cluster health.

Examples

Check overall cluster health.

Elasticsearch

GET /_cluster/health

Check health of a specific index.

Elasticsearch

GET /_cluster/health/my_index

Wait up to 30 seconds for the cluster to become green.

Elasticsearch

GET /_cluster/health?wait_for_status=green&timeout=30s

Sample Program

This command asks Elasticsearch to show the cluster health in a readable format.

Elasticsearch

curl -X GET "localhost:9200/_cluster/health?pretty"

Important Notes

Green status means your cluster is fully reliable and all data is available.

Yellow status means your data is safe but some replicas are not assigned, so if a node fails, data might be temporarily unavailable.

Red status means some data is missing or not accessible, which can cause errors or data loss.

Summary

Cluster health tells you if your Elasticsearch system is working well.

Green means all good, yellow means caution, red means problems.

Checking cluster health helps keep your data safe and your searches fast.