ALM-19014 Capacity Quota Usage on ZooKeeper Exceeds the Threshold Severely

Alarm Description

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

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

Alarm Attributes

Alarm Parameters

Impact on the System

This alarm indicates that the capacity 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.

Handling Procedure

Check the capacity configuration and usage of ZNodes.

1. On FusionInsight Manager, choose O&M > Alarm > Alarms, select the alarm whose ID is 19014, and view the threshold in Additional Information.
2. 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).

3. Run the hbase zkcli command to log in to the ZooKeeper client and run the listquota /hbase command to check the ZNode capacity 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 capacity configuration of the root ZNode of the HBase service.

   

4. 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.

5. On FusionInsight Manager, choose O&M > Alarm > Alarms. Check whether the alarm whose ID is 12007, 19000, or 19013 and the 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.

6. 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.

7. 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.

8. Check whether the alarm is cleared five minutes later.
   • If yes, no further action is required.
   • If no, go to 9.

Collect fault information.

9. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
10. Expand the Service drop-down list, and select HBase for the target cluster.
11. Click the edit icon 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.
12. Contact O&M engineers and provide the collected logs.

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

Related Information

None.