Technologies/Elasticsearch/elasticsearch.cluster.state_update.count
ElasticsearchElasticsearchMetric

elasticsearch.cluster.state_update.count

Cluster state update count
Dimensions:None
Available on:OpenTelemetryOpenTelemetry (1)

Summary

Counts cluster state update operations processed by the master node. Every index creation, shard allocation, mapping change, or node join/leave triggers a state update. High update rates can overwhelm the master node and delay critical operations. Monitoring this helps identify cluster churn from excessive index creation or unstable nodes.

Interface Metrics (1)
OpenTelemetryOpenTelemetry
The number of cluster state update attempts that changed the cluster state since the node started.
Dimensions:None
Sources
elasticsearch.cluster.state_update.countgithub.com
Related Insights (2)
Mapping Explosion Cluster State Bloatcritical

Using high-cardinality data (like user IDs or timestamps) as JSON keys causes unbounded field creation in index mappings, bloating cluster state to hundreds of megabytes and causing master node instability and broadcast delays.

▸
Cluster State Update Delayswarning

Slow cluster state updates cause delays in shard allocation, index creation, and mapping updates. Large cluster state size or master node resource constraints are common causes.

▸