The system checks the hdfs://hacluster/hbase/corrupt directory on the HDFS of each HBase service every 120 seconds. This alarm is generated when there are WAL files in the /hbase/corrupt directory.
This alarm is cleared when the /hbase/corrupt directory does not exist or does not contain WAL files.
This alarm applies only to MRS 3.3.0 or later.
hdfs://hacluster indicates the name of the file system used by HBase, and /hbase indicates the root directory of HBase in the file system. You can log in to FusionInsight Manager, choose Cluster > Services > HBase and click Configuration. Search for fs.defaultFS and hbase.data.rootdir.
Alarm ID |
Alarm Severity |
Auto Cleared |
---|---|---|
19026 |
Major |
Yes |
Parameter |
Description |
---|---|
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. |
There are damaged WAL files in HBase, which may cause data loss.
The WAL files are damaged.
cd Client installation directory
source bigdata_env
kinit Component service user (If Kerberos authentication is disabled for the cluster (the cluster is in normal mode), skip this step.)
hdfs dfs -ls hdfs://hacluster/hbase/corrupt/*%2C*
Collect fault information.
This alarm is automatically cleared after the fault is rectified.
None.