Q: You have an ELK stack. The Elasticsearch cluster status turns Yellow. What does this mean, and what do you do?
Elasticsearch cluster states are:
Want to master this scenario in a live sandbox? The Linux Foundation's Prometheus Certified Associate (PCA) & Monitoring Labs covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "In an interview, I explain how we designed actionable, symptom-based alerting using the Four Golden Signals. The interviewer is testing: Elasticsearch shard mechanics, replica management.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
Elasticsearch cluster states are:
- Green: All primary and replica shards are allocated.
- Yellow: All primary shards are allocated (data is safe, searching works), but one or more replica shards are unassigned.
- Red: One or more primary shards are missing (data loss or downtime).
Remediation & Permanent Safeguards
A Yellow state usually happens because a node went down or restarted, and ES cannot allocate the replica shard to the same node holding the primary shard. To fix:
- Check
_cat/healthand_cluster/allocation/explainto see *why* and *which* shards aren't allocating. - The usual cause is either an offline node (I need to bring it back up, or wait for ES to timeout and recreate the replica on another node if there's space) or a disk watermark issue (disks are >85% full, preventing new shard allocation, so I need to clear old indices or add disk space).
- Green: All primary and replica shards are allocated.
- Yellow: All primary shards are allocated (data is safe, searching works), but one or more replica...
- Red: One or more primary shards are missing (data loss or downtime).
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Injecting high-cardinality label dimensions (such as user IDs or request UUIDs) into Prometheus metrics when configuring Observability stack Elasticsearch High-cardinality label values cause exponential time-series growth, consuming gigabytes of TSDB memory and crashing Prometheus servers.
- Evaluating application performance solely through arithmetic mean or p50 latency while ignoring tail latency (p99) when configuring Observability stack Elasticsearch Averages hide catastrophic tail latency outages where 1% of high-value user transactions suffer severe timeouts.
- Failing to inject and extract W3C distributed trace context across message brokers and RPC calls when configuring Observability stack Elasticsearch Breaking distributed trace context propagation fragments end-to-end transaction waterfalls into disconnected, un-correlatable trace segments.
- Configuring alert rule evaluation intervals without sufficient duration damping (for: 5m), inducing alert flap when configuring Observability stack Elasticsearch Instant alerts triggered by transient sub-second CPU or latency blips page on-call engineers unnecessarily and dilute response urgency.