ALM-27003 DBService Heartbeat Interruption Between the Active and Standby Nodes

Alarm Description

This alarm is generated when the active or standby DBService node has not received heartbeat messages from the peer node for 7 seconds.

This alarm is cleared when the heartbeat recovers.

Alarm Attributes

Alarm Parameters

Impact on the System

During the DBService heartbeat interruption, only one node can provide the service. If this node is faulty, no standby node is available for failover and the service is unavailable.

Possible Causes

The link between the active and standby DBService nodes is abnormal.

Handling Procedure

Check whether the network between the active and standby DBService servers is normal.

1. In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and click to view the IP address of the standby DBService server for which the alarm is generated.
2. Log in to the active DBService server as user root.

3. Run the ping heartbeat IP address of the standby DBService command to check whether the standby DBService server is reachable.
   • If yes, go to 6.
   • If no, go to 4.

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

5. Rectify the network fault and check whether the alarm is cleared from the alarm list.
   • If yes, no further action is required.
   • If no, go to 6.

Collect fault information.

6. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
7. Expand the Service drop-down list, and select the following services for the target cluster
   • DBService
   • Controller
   • NodeAgent

8. 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.
9. Contact O&M engineers and provide the collected logs.

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

Related Information

None.