Help Center/ MapReduce Service/ User Guide (Ankara Region)/ Alarm Reference/ ALM-45585 IoTDB Service Unavailable
Updated on 2024-11-29 GMT+08:00
View PDF
Share

ALM-45585 IoTDB Service Unavailable

Alarm Description

The system checks the IoTDB service status every 300 seconds. This alarm is generated when the IoTDB service is unavailable. This alarm is cleared when the IoTDB service recovers.

Alarm Attributes

Alarm ID

Alarm Severity

Alarm Type

Service Type

Auto Cleared

45585

Critical

Error handling

IoTDB

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.

Additional Information

Details

Specifies additional alarm information.

Impact on the System

Users cannot use the IoTDB service properly.

Possible Causes

  • The KrbServer service is abnormal.
  • More than 50% of IoTDBServer instances are faulty.
  • Failed to connect to the IoTDBServer JMX. As a result, the node status cannot be obtained.
  • A disk is aged or damaged.

Handling Procedure

Check whether the KrbServer service on which the IoTDB depends is abnormal.

  1. On FusionInsight Manager, choose O&M > Alarm > Alarms. In the alarm list, view the host name and IP address in Location of the alarm whose ID is 45585.
  2. In the alarm list, check whether ALM-25500 KrbServer Service Unavailable exists.

    • If yes, go to 3.
    • If no, go to 5.

  3. Handle the alarm by referring to ALM-25500 KrbServer Service Unavailable.
  4. After ALM-25500 is cleared, wait several minutes and check whether this alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 5.

Check whether IoTDBServer instances are faulty.

  1. On FusionInsight Manager, choose Cluster > Services > IoTDB > Instance.
  2. Check whether the percentage of faulty IoTDBServer instances exceeds 50%. If yes, restart the faulty IoTDBServer instances and check whether the status is restored.

    • If yes, no further action is required.
    • If no, go to 7.

Check whether the IoTDBServer instance is started properly.

  1. Log in to the host obtained in 1, switch to user omm, and run the jps command to check whether the IoTDBServer process exists in the command output.

    • If yes, no further action is required.
    • If no, go to 8.

  1. On FusionInsight Manager, choose Cluster > Services > IoTDB > Instance, select the IoTDBServer instance for which this alarm is generated, click More, and select Restart Instance.
  2. After the instance is restarted, wait several minutes and check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 10.

Check disks.

  1. Check whether the disks of the host for which the alarm is generated exist, or check whether the disks can be used properly after being moved to another host.

    • If yes, no further action is required.
    • If no, go to 11.

Collect fault information.

  1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
  2. Expand the Service drop-down list, select IoTDB for the target cluster, and click OK.
  3. 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.
  4. Contact O&M engineers and provide the collected logs.

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

Related Information

None.

Parent topic: Alarm Reference