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 (75% by default).

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

   For details about how to log in to FusionInsight Manager, see Accessing MRS Manager.

2. Log in to the node where the HBase client is installed as user root and run the following commands:

   Go to the client installation directory.

   cd Client installation directory

   Configure environment variables.

   source bigdata_env

   If Kerberos authentication is enabled for the cluster (in 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. Log in to the ZooKeeper client and check the ZNode capacity quota of the HBase service.
   1. Log in to the ZooKeeper client.

      hbase zkcli

   2. Check the ZNode capacity quota of the HBase service.

      listquota /hbase

      /hbase indicates the root ZNode directory of HBase in ZooKeeper. You can obtain the directory by searching for the zookeeper.znode.parent parameter on the parameter configuration page of the HBase service.

      For example, the marked area in the following figure shows the root ZNode capacity configuration of the HBase service.

      

4. Run the following command to check the capacity usage of the /hbase/splitWAL ZNode and check whether the ratio of Data size to the root ZNode capacity quota is close to the alarm threshold.

   getusage /hbase/splitWAL

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

5. On Manager, choose O&M > Alarm > Alarms. Check whether there is an alarm whose ID is 12007, 19000, or 19013 and whose ServiceName in Location is the current HBase service.
   • If yes, click View Help next to the alarm and rectify the fault by referring to the help document. Then, go to Step 8.
   • If no, go to Step 9.

6. Run the following command to check the capacity usage of the /hbase/replication ZNode and check whether the ratio of Data size to the root ZNode capacity quota is close to the alarm threshold.

   getusage /hbase/replication

   • If yes, go to Step 7.
   • If no, go to Step 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 Step 8.
   • If no, go to Step 9.

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

Collect the fault information.

9. On Manager, choose O&M > Log > Download.
10. Expand the drop-down list next to the Service field. In the Services dialog box that is displayed, select HBase for the target cluster.
11. 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.
12. Contact O&M personnel and provide the collected logs.

Alarm Clearing

This alarm is automatically cleared after the fault is rectified.

Related Information

None