ALM-45482 Abnormal Kudu Table Status

Alarm Description

This alarm is generated when the system detects that a table in the Kudu database is abnormal.

This alarm is cleared when all tables in the Kudu database are normal.

Alarm Attributes

Alarm Parameters

Impact on the System

If a data table is faulty, data may be unavailable, and data inconsistency may occur.

Possible Causes

The Kudu service or instance is abnormal, or the network, node, or disk is faulty.

Handling Procedure

Check whether the Kudu service or instance is abnormal.

1. Log in to FusionInsight Manager, choose Cluster > Services, and check whether the Kudu service or instance is abnormal.
   • If yes, go to Step 2.
   • If no, go to Step 3.

2. Restart the Kudu service or instance and then check whether the alarm is cleared.
   • If yes, no further action is required.
   • If no, go to Step 3.

Check whether the network connection is abnormal.

3. Contact the network administrator to check whether the network is faulty.
   • If yes, go to Step 4.
   • If no, go to Step 5.

4. Rectify the network fault and then check whether the alarm is cleared.
   • If yes, no further action is required.
   • If no, go to Step 5.

Check whether the node is faulty.

5. In the alarm list, check whether there is the ALM-12006 Node Fault alarm.
   • If yes, rectify the fault by referring to the node alarm help and go to Step 6.
   • If no, go to Step 7.

6. Check whether the alarm is cleared a few minutes later.
   • If yes, no further action is required.
   • If no, go to Step 7.

Check whether the disk is faulty.

7. In the alarm list, check whether there is the ALM-12017 Insufficient Disk Capacity or ALM-12063 Unavailable Disk alarm.
   • If yes, rectify the fault by referring to the corresponding alarm help and go to Step 8.
   • If no, go to Step 9.

8. Check whether the alarm is cleared a few minutes later.
   • If yes, no further action is required.
   • If no, go to Step 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, select Kudu for the target cluster, and click OK.
11. Click the edit icon in the upper right corner, and set Start Date and End Date for log collection to 30 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
12. Send the collected fault logs to O&M personnel for help.

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

Related Information

None.