Why Is My Elasticsearch Cluster Consuming 15 GB Heap? A Deep Dive into Memory, Sharding, and Performance Bottlenecks
A 7‑node Elasticsearch cluster handling 500 million documents shows excessive heap usage, many deleted documents, high translog size, saturated OS memory, and inefficient sharding, prompting a detailed analysis of stats, root‑cause identification, and concrete recommendations for mapping, shard design, and JVM tuning.
