Zookeeper Workload Test

Sudden spikes noticed in the resource usage patterns of the Apache Zookeeper may be due to a variety of reasons such as network issues, misconfiguration of the target Apache Zookeeper, multiple client requests that are queued up etc. For an Apache Zookeeper administrator, it is essential to proactively avert such issues. For this, they rely on monitoring the resource utilization pattern of the Apache Zookeeper round the clock. The Zookeeper Workload test helps administrators in this regard.

This test reports the CPU and memory utilization of the target Apache Zookeeper. Using this test, administrators can analyze resource usage patterns of the Apache Zookeeper and isolate bottlenecks, if any.

Target of the test : Apache Zookeeper server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for the target Apache Zookeeper server being monitored.

Configurable parameters for the test

Parameter	Description
Test period	How often should the test be executed
Host	The IP address of the host for which this test is to be configured.
Port	The port at which the target Apache Zookeeper server listens to.
PID File Location	For the eG agent to collect the required metrics, you need to specify the full path to the file in which the Process ID of the target Apache Zookeeper server is stored. For example, the file location can be /opt/zookeeper/apache-zookeeper-3.6.3-bin/data/zookeeper_server.pid.

Measurements made by the test

Measurement	Description	Measurement Unit	Interpretation
CPU utilization	Indicates the CPU utilized by the target Apache Zookeeper.	Percent	A high value for this measure is a cause of concern. A few probable reasons for such high CPU utilization may be network issues, misconfiguration of the target Zookeeper, authentication issues on the server on which the Zookeeper is installed etc. Administrators need to further investigate the issues and rectify them so that the CPU utilization is optimal at all times.
Memory utilization	Indicates the memory utilized by the target Apache Zookeeper.	Percent	A high value for this measure is a cause of concern. This could be due to numerous queued requests from the clients to the Apache Zookeeper within a short duration. To keep the memory utilization of the Apache Zookeeper within acceptable limits, administrators should fine-tune the Zookeeper to throttle clients so that there is no more outstanding requests.