<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Fixing Yellow Shards in Elasticsearch :: Forensic wheels</title><link>https://polymathmonkey.github.io/weblog/artifacts/yellowshardsinelastic/index.html</link><description>Introduction If you’re running Elasticsearch on a single node — like a Raspberry Pi or small lab setup like I am — you might notice some indices appear with a yellow health status.
This show article explains what that means and how to fix it, especially in resource-constrained, single-node environments.
What Does “Yellow” Mean? In Elasticsearch:
green: All primary and replica shards are assigned and active. yellow: All primary shards are active, but at least one replica shard is unassigned. red: At least one primary shard is missing → critical! Why Yellow Happens on Single Nodes In single-node clusters, Elasticsearch cannot assign replica shards (because replicas must be on a different node). So any index with replicas will always be yellow unless:</description><generator>Hugo</generator><language>en-us</language><copyright>All text is licensed under a Creative Commons Attribution 4.0 International License.</copyright><lastBuildDate/><atom:link href="https://polymathmonkey.github.io/weblog/artifacts/yellowshardsinelastic/index.xml" rel="self" type="application/rss+xml"/></channel></rss>