ALM-45475 A Single Replica Exists in the Kudu Data Table

The system checks the replica status of the Kudu data table. This alarm is generated when a single replica is detected in the Kudu data table.

This alarm is cleared when all Kudu data tables have multiple replicas or no data.

Alarm ID	Alarm Severity	Auto Cleared
45475	Major	Yes

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.

A hardware fault, for example, a slow disk or a faulty disk, may cause Kudu data loss.

Log in to the node where the MRS cluster client is installed as user root and switch to user omm.

su - omm
Initialize the client.

source /opt/Bigdata/client/bigdata_env
If Kerberos authentication (in security mode) is enabled for the cluster, run the following command to authenticate the user. If Kerberos authentication (in normal mode) is not enabled for the cluster, skip this step.

kinit {Username}
Run the following command to check whether there is a table whose RF is 1:

kudu cluster ksck <master_addresses>

master_addresses: The value is in the format of KuduMaster service IP address 1:7051,KuduMaster service IP address 2:7051,KuduMaster service IP address 3:7051.

KuduMaster service IP address: You can log in to FusionInsight Manager and choose Cluster > Services > Kudu > Instances to view the service IP address of the KuduMaster instance.
- If yes, consider whether to keep the single-replica table. You are advised to recreate the table and select at least three replicas for it.
- If no, go to Step 5.

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.
Send the collected fault logs to O&M personnel for help.