Updated on 2022-12-14 GMT+08:00

ALM-19016 Quantity Quota Usage on ZooKeeper Exceeds the Threshold Severely

Alarm description

The system checks the ZNode usage of HBase every 120 seconds. This alarm is generated when the ZNode quantity usage of HBase exceeds the "Critical" alarm threshold (90% by default).

This alarm is cleared when the quantity usage of the ZNode is less than the "Critical" alarm threshold.

If the multi-instance function is enabled in the cluster and multiple HBase services are installed, determine the HBase service for which the alarm is generated based on the value of ServiceName in Location of the alarm. For example, if Service name is HBase-1 in Location, change the operation object in the handling procedure from HBase to HBase-1.

Attribute

Alarm ID

Alarm Severity

Automatically Cleared

19016

Critical

Yes

Parameters

Name

Meaning

Source

Specifies the cluster for which the alarm is generated.

ServiceName

Specifies the service for which the alarm is generated.

RoleName

Specifies the role for which the alarm is generated.

HostName

Specifies the host for which the alarm is generated.

Threshold

Specifies the threshold for which the alarm is generated.

Impact on the System

This alarm indicates that the quantity usage of the ZNode of HBase has exceeded the threshold severely. As a result, the write request of the HBase service fails.

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.

Procedure

Check the quantity quota and usage of ZNodes.

  1. On FusionInsight Manager, choose O&M > Alarm > Alarms. Select the alarm whose ID is "19016", and view the threshold in Additional Information.
  2. Log in to the HBase client as user root. Run the following command to access 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 version, run the following command to perform security authentication:

    kinit hbase

    Enter the password as prompted (obtain the password from the administrator).

  3. Run the hbase zkcli command to log in to the ZooKeeper client and run the listquota /hbase command to view 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.

  4. Run the getusage /hbase/splitWAL command to check the quantity usage of the ZNode. Check whether the ratio of "Node count" in the command output to the ZNode quantity quota is close to the alarm threshold.

    • If yes, go to 5.
    • If no, go to 6.

  5. On FusionInsight Manager, choose O&M > Alarm > Alarms. 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 on the right of the alarm and rectify the fault by referring to the help document. Then, go to 8.
    • If no, go to 9.

  6. Run the getusage /hbase/replication command to check the usage of the ZNodes. Check whether the ratio of "Node count" in the command output to the ZNode quantity quota is close to the alarm threshold.

    • If yes, go to 7.
    • If no, go to 9.

  7. On FusionInsight Manager, choose O&M > Alarm > Alarms. Check whether the alarm whose Alarm ID is "19006" and ServiceName in Location is the current HBase service exists.

    • If yes, click View Help on the right of the alarm and rectify the fault by referring to the help document. Then, go to 8.
    • If no, go to 9.

  8. Check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 9.

Collect fault information.

  1. On FusionInsight Manager, choose O&M > Log > Download.
  2. In the Service area, select HBase of the cluster to be operated.
  3. 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.
  4. Contact the O&M personnel and provide the collected logs.

Alarm Clearing

After the fault is rectified, the system automatically clears this alarm.

Related Information

None