In Elasticsearch, the cluster health API returns a status. What does the status 'green' mean for the cluster?
GET /_cluster/health
Think about what full reliability means for data availability.
A green status means all shards, including replicas, are assigned and active. This ensures no data loss and full reliability.
Why do unassigned shards in an Elasticsearch cluster reduce its reliability?
Think about what happens if a node with primary data fails and replicas are missing.
Unassigned shards mean some data is not currently stored on any node. If the node holding the primary shard fails, data could be lost, reducing reliability.
Given this cluster health response, why is the status 'yellow'?
{"status":"yellow","number_of_nodes":3,"active_primary_shards":10,"active_shards":15,"relocating_shards":0,"initializing_shards":0,"unassigned_shards":5}Yellow means primary shards are fine but replicas have issues.
A yellow status means all primary shards are active, but some replica shards are unassigned. This means data is available but not fully redundant.
Which of the following is the correct syntax to check cluster health using Elasticsearch REST API?
The cluster health API uses a GET request with a specific path.
The correct endpoint is GET /_cluster/health. Other options are invalid paths or wrong HTTP methods.
In a multi-node Elasticsearch cluster, how does the cluster health status directly impact data reliability and availability?
Consider what full replication means for fault tolerance.
Green status means all primary and replica shards are assigned and active, so data is safe and available even if a node fails. Yellow or red indicate problems that risk data loss or unavailability.