ALM-19017 Capacity Quota Usage on ZooKeeper Exceeds the Threshold

Alarm Description

The system checks the ZNode usage of the HBase service every 120 seconds. This alarm is generated when the system detects that the ZNodes capacity usage of the HBase service exceeds the alarm threshold (75% by default).

This alarm is cleared when the capacity usage of the ZNode capacity is less than the threshold.

Alarm Attributes

Alarm ID	Alarm Severity	Auto Cleared
19017	Major	Yes

Alarm Parameters

Parameter	Description
Source	Specifies the cluster for which the alarm was generated.
ServiceName	Specifies the service for which the alarm was generated.
RoleName	Specifies the role for which the alarm was generated.
HostName	Specifies the host for which the alarm was generated.
Threshold	Specifies the threshold for generating the alarm.

Impact on the System

This alarm indicates that the ZNodes capacity usage in the HBase service has exceeded the threshold. If this alarm is not handled in a timely manner, the problem severity may be escalated to Critical, affecting data writing.

Possible Causes

DR is configured for HBase, and data synchronization fails or is slow in DR.
A large number of WAL files are being split in the HBase cluster.

Handling Procedure

Check the capacity configuration and usage of ZNodes.

On FusionInsight Manager, choose O&M > Alarm > Alarms, select the alarm whose ID is 19017, and view the threshold in Additional Information.
Log in to the HBase client as user root. Run the following command to go to the client installation directory:

cd Client installation directory

Run the following command to set environment variables:

source bigdata_env

If the cluster uses the security mode, run the following command to perform security authentication:

kinit hbase

Enter the password as prompted (obtain the password from the MRS cluster administrator).
Run the hbase zkcli command to log in to the ZooKeeper client and run the listquota /hbase command to check the ZNode quantity quota of the HBase service. The ZNode root directory in the command is specified by the zookeeper.znode.parent parameter of the HBase service. The marked area in the following figure shows the quantity configuration of the root ZNode of the HBase service.
Run the getusage /hbase/splitWAL command to check the capacity usage of the ZNode. Check whether the ratio of Data size to the ZNode capacity quota is close to the alarm threshold.
- If yes, go to 5.
- If no, go to 6.
On FusionInsight Manager, check whether the alarm whose ID is 12007, 19000, or 19013 and ServiceName in Location is the current HBase service exists.
- If yes, click View Help next to the alarm and rectify the fault by referring to the help document. Then, go to 8.
- If no, go to 7.
Run the getusage /hbase/replication command to check the capacity usage of the ZNode. Check whether the ratio of Data size to the ZNode capacity quota is close to the alarm threshold.
- If yes, go to 7.
- If no, go to 9.
On FusionInsight Manager, choose O&M > Alarm > Alarms. Check whether the alarm whose ID is 19006 and ServiceName in Location is the current HBase service exists.
- If yes, click View Help next to the alarm and rectify the fault by referring to the help document. Then, go to 8.
- If no, go to 9.
Check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to 9.

Collect the fault information.

On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
Expand the Service drop-down list, and select HBase for the target cluster.
Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
Contact O&M personnel and provide the collected logs.