Imbalanced Client Connections Overload Individual Nodes
infoResource ContentionUpdated Feb 6, 2026
When client connections are not evenly distributed across ensemble members, some nodes become overloaded while others remain underutilized, leading to performance degradation on heavily loaded nodes.
Sources
How to Monitor Zookeeper Ensemble Health with the Collectoroneuptime.com
How to Monitor ZooKeeper: Key Metrics & Best Tools in 2023sematext.com
Configuring and Monitoring Zookeeper with OpenTelemetry Receiveropenobserve.ai
End-to-End Guide: Configuring and Monitoring Zookeeper with OpenTelemetry Receiveropenobserve.ai
Apache ZooKeeper Monitoring | Atatusatatus.com
How to Configure the Zookeeper Receiver in the OpenTelemetry ...oneuptime.com
ZooKeeper Monitoring - Netdatawww.netdata.cloud
Technologies:
How to detect:
Monitor zookeeper.connection.active across all ensemble nodes. Alert when one node has >50% more connections than the average, or when connection count on any node approaches maxClientCnxns setting (default 60).
Recommended action:
Review client connection configuration - ensure clients have all ensemble member addresses and are not hardcoded to connect to a single node. Verify load balancers (if used) are distributing connections evenly. Adjust maxClientCnxns if needed, but investigate why connections are concentrated first.