ALM-45652 Flink Service Unavailable
This section applies to MRS 3.3.0 or later.
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 |
Auto Cleared |
---|---|---|
45652 |
Critical |
Yes |
Alarm Parameters
Parameter |
Description |
---|---|
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.
- Log in to FusionInsight Manager and choose O&M > Alarm > Alarms.
- In the alarm list, check whether "ALM-13000 ZooKeeper Service Unavailable" exists.
- Handle the alarm by referring to "ALM-13000 ZooKeeper Service Unavailable."
- 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.
- On FusionInsight Manager, choose O&M > Alarm > Alarms.
- In the alarm list, check whether "ALM-14000 HDFS Service Unavailable" exists.
- Handle the alarm by referring to "ALM-14000 HDFS Service Unavailable."
- 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.
- On FusionInsight Manager, choose O&M > Alarm > Alarms.
- In the alarm list, check whether "ALM-18000 Yarn Service Unavailable" exists.
- Handle the alarm by referring to "ALM-18000 Yarn Service Unavailable."
- 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.
- On FusionInsight Manager, choose O&M > Alarm > Alarms.
- In the alarm list, check whether "ALM-25500 KrbServer Service Unavailable" exists.
- Handle the alarm by referring to "ALM-25500 KrbServer Service Unavailable."
- 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.
- On FusionInsight Manager, choose O&M > Alarm > Alarms.
- In the alarm list, check whether "ALM-27001 DBService Service Unavailable" exists.
- Handle the alarm by referring to "ALM-27001 DBService Service Unavailable."
- 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.
- On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
- Expand the Service drop-down list, and select Flink for the target cluster.
- 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.
- Contact O&M personnel and provide the collected logs.
Alarm Clearance
This alarm is automatically cleared after the fault is rectified.
Related Information
None.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot