- Releases Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- SQL Developer Guide
- Python Developer Guide
- ETL Developer Guide
- FAQ
- Contact Us
- Releases Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- SQL Developer Guide
- Python Developer Guide
- ETL Developer Guide
- FAQ
- Contact Us
Overview
The JobManager of a Flink job manages and schedules the whole job. If its CPU load is too high, various exceptions may occur in the job. This event is triggered when the JobManager of the job is almost fully loaded for a long period of time.
Note
This feature is in beta testing, so custom rules are not supported. This capability will be available in the future.
Trigger conditions
The system detects the CPU utilization of the JobManager of a Flink job every 5 minutes.
If the CPU utilization of the JobManager exceeds 80% in 5 consecutive data points, its CPU load is considered to be too high.
Note
To avoid frequent alarms, at most one push of this event can be triggered per hour for each running instance ID of each job.
Alarm configuration
You can configure an alarm policy as instructed in Configuring Event Alarms (Events) for this event to receive trigger and clearing notifications in real time.
Suggestions
The reasons for a too-high JobManager CPU load are complicated. We recommend you configure more resources for the job as instructed in Configuring Job Resources, setting a larger JobManager spec, for example.
Yes
No
Was this page helpful?