Updated on 2024-11-29 GMT+08:00

ALM-45652 Flink Service Unavailable

Alarm Description

The alarm module checks the Flink status every 60 seconds. This alarm is generated when the Flink service is unavailable. This alarm is cleared when the Flink service recovers.

Alarm Attributes

Alarm ID

Alarm Severity

Alarm Type

Service Type

Auto Cleared

45652

Critical

Environment

Flink

Yes

Alarm Parameters

Type

Parameter

Description

Location Information

Source

Specifies the cluster for which the alarm is generated.

ServiceName

Specifies the service for which the alarm is generated.

RoleName

Specifies the role for which the alarm is generated.

HostName

Specifies the job for which the alarm is generated.

Impact on the System

Flink jobs cannot be submitted with FlinkServer and the Flink client.

Possible Causes

The ZooKeeper, HDFS, Yarn, KrbServer, or DBService service on which Flink depends is unavailable.

Handling Procedure

Check whether the ZooKeeper service on which Flink depends is abnormal.

  1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms.
  2. In the alarm list, check whether "ALM-13000 ZooKeeper Service Unavailable" exists.

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

  3. Handle the alarm by referring to "ALM-13000 ZooKeeper Service Unavailable."
  4. After the alarm is cleared, wait a few minutes and check whether the alarm is cleared.

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

Check whether the HDFS service on which Flink depends is abnormal.

  1. On FusionInsight Manager, choose O&M > Alarm > Alarms.
  2. In the alarm list, check whether "ALM-14000 HDFS Service Unavailable" exists.

    • If yes, go to 7.
    • If no, go to 9.

  3. Handle the alarm by referring to "ALM-14000 HDFS Service Unavailable."
  4. After the alarm is cleared, wait a few minutes and check whether the alarm is cleared.

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

Check whether the Yarn service on which Flink depends is abnormal.

  1. On FusionInsight Manager, choose O&M > Alarm > Alarms.
  2. In the alarm list, check whether "ALM-18000 Yarn Service Unavailable" exists.

    • If yes, go to 11.
    • If no, go to 13.

  3. Handle the alarm by referring to "ALM-18000 Yarn Service Unavailable."
  4. After the alarm is cleared, wait a few minutes and check whether the alarm is cleared.

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

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

  1. On FusionInsight Manager, choose O&M > Alarm > Alarms.
  2. In the alarm list, check whether "ALM-25500 KrbServer Service Unavailable" exists.

    • If yes, go to 15.
    • If no, go to 17.

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

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

Check whether the DBService service on which Flink depends is abnormal.

  1. On FusionInsight Manager, choose O&M > Alarm > Alarms.
  2. In the alarm list, check whether "ALM-27001 DBService Service Unavailable" exists.

    • If yes, go to 19.
    • If no, go to 21.

  3. Handle the alarm by referring to "ALM-27001 DBService Service Unavailable."
  4. After the alarm is cleared, wait a few minutes and check whether the alarm is cleared.

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

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, and select Flink for the target cluster.
  3. Click 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.