Frequent Leader Elections Indicate Cluster Instability
warningreliabilityUpdated Feb 9, 2026
Multiple leader changes within a short timeframe signal network issues, resource contention, or disk latency problems. Each election disrupts write operations and degrades cluster performance.
Sources
Technologies:
How to detect:
Monitor etcd_server_leader_changes_seen_total for increases. Alert when rate exceeds 3 changes per hour. Check logs for 'leader' messages and track etcd_server_has_leader going to 0.
Recommended action:
Investigate root cause: check disk latency metrics (etcd_disk_wal_fsync_duration_seconds), network latency between peers (etcd_network_peer_round_trip_time_seconds), and resource pressure (CPU/memory). Fix network partitions, reduce disk contention, or adjust heartbeat/election timeouts if network latency is consistently high.