Technologies/Elasticsearch/elasticsearch.node.shards.size
ElasticsearchElasticsearchMetric

elasticsearch.node.shards.size

Node shard size bytes
Dimensions:None
Available on:OpenTelemetryOpenTelemetry (1)

Summary

Reports the total size of all shards stored on a node, measuring the aggregate disk space consumed by primary and replica shards. This metric is fundamental for capacity planning and node balancing. Uneven distribution across nodes may indicate shard allocation imbalances, while rapid growth signals indexing activity that may eventually trigger disk watermark thresholds (as documented in the "Disk Watermark Shard Relocation Storm" insight).

Interface Metrics (1)
OpenTelemetryOpenTelemetry
The size of the shards assigned to this node.
Dimensions:None
Sources
elasticsearch.node.shards.sizegithub.com

Technical Annotations (6)

Configuration Parameters (1)
element_typerecommended: bfloat16
For dense_vector fields where storage reduction outweighs precision loss
Technical References (5)
wildcard field typesconceptbinary doc valuescomponentZstd compressionprotocoldense_vectorcomponentbfloat16concept
Related Insights (4)
Excessive Shard Count Degrading Performancecritical

Too many shards consume cluster resources even when idle, causing slow queries, increased overhead, and reduced stability. Rule of thumb: keep shards below 20 per GB of heap configured.

▸
Node Role Imbalance Causing Hotspotswarning

Improper distribution of shards or unbalanced node roles can cause resource hotspots where some nodes are overloaded while others are underutilized.

▸
Binary doc values compression can reduce storage footprint for wildcard fieldsinfo
▸
Bfloat16 vector storage reduces memory by 50% with precision tradeoffinfo
▸