Help Center>
Data Lake Insight>
FAQs>
Flink Jobs>
O&M Guide>
Why Is the Flink Job Abnormal Due to Heartbeat Timeout Between JobManager and TaskManager?
Updated on 2023-05-19 GMT+08:00
Why Is the Flink Job Abnormal Due to Heartbeat Timeout Between JobManager and TaskManager?
Symptom
JobManager and TaskManager heartbeats timed out. As a result, the Flink job is abnormal.
Figure 1 Error information
![Click to enlarge](https://support.huaweicloud.com/eu/dli_faq/en-us_image_0000001391536818.png)
Possible Causes
- Check whether the network is intermittently disconnected and whether the cluster load is high.
- If Full GC occurs frequently, check the code to determine whether memory leakage occurs.
Figure 2 Full GC
Handling Procedure
- If Full GC occurs frequently, check the code to determine whether memory leakage occurs.
- Allocate more resources for a single TaskManager.
- Contact technical support to modify the cluster heartbeat configuration.
Parent topic: O&M Guide
O&M Guide FAQs
- How Do I Locate a Flink Job Submission Error?
- How Do I Locate a Flink Job Running Error?
- How Do I Know Whether a Flink Job Can Be Restored from a Checkpoint After Being Restarted?
- Why Does DIS Stream Not Exist During Job Semantic Check?
- Why Is the OBS Bucket Selected for Job Not Authorized?
- Why Are Logs Not Written to the OBS Bucket After a DLI Flink Job Fails to Be Submitted for Running?
- How Do I Configure Connection Retries for Kafka Sink If it is Disconnected?
- Why Is Information Displayed on the FlinkUI/Spark UI Page Incomplete?
- Why Is the Flink Job Abnormal Due to Heartbeat Timeout Between JobManager and TaskManager?
- Why Is Error "Timeout expired while fetching topic metadata" Repeatedly Reported in Flink JobManager Logs?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
more