ALM-45478 Kudu Failed Data Balancing

Alarm Description

The system periodically balances data among Kudu data tables. This alarm is generated when the system detects that the data balancing API returns a failure response.

This alarm is cleared when the Kudu data balancing API is successfully called.

Alarm Attributes

Alarm ID	Alarm Severity	Auto Cleared
45478	Major	Yes

Alarm Parameters

Type	Parameter	Description
Location Information	Source	Specifies the cluster for which the alarm was generated.
	ServiceName	Specifies the service for which the alarm was generated.
	RoleName	Specifies the role for which the alarm was generated.
	HostName	Specifies the host for which the alarm was generated.

Impact on the System

Failed to call the data balancing API. The Kudu component may be abnormal.

Possible Causes

The segment or replica in the Kudu data table is lost.

Handling Procedure

Handle the Kudu instance exception.

On FusionInsight Manager, choose O&M > Alarm > Alarms. On the displayed page, locate alarm ALM-45478 Kudu Failed Data Balancing.
In the Location field, record the host name and role name.
Choose Cluster > Services > Kudu > Instances. Click the role name for the host name obtained in 2 and restore the instance. Then, check whether the alarm is cleared.
- If yes, go to 4.
- If no, go to 5.
Choose O&M > Alarm > Alarms and check whether the alarm is cleared.
- If yes, no further action is required.
- If no, go to 5.
On the Kudu web UI, check whether any segment or replica is missing.

Collect fault information.

On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.

Expand the Service drop-down list, and select Kudu for the target cluster.
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.
Contact O&M personnel and provide the collected logs.