Help Center>
Data Lake Insight>
FAQs>
Flink Jobs>
O&M Guide>
How Do I Locate a Flink Job Submission Error?
Updated on 2023-05-19 GMT+08:00
How Do I Locate a Flink Job Submission Error?
- On the Flink job management page, hover the cursor on the status of the job that fails to be submitted to view the brief information about the failure.
The possible causes are as follows:
- Insufficient CUs: Increase the number of CUs of the queue.
- Failed to generate the JAR file: Check the SQL syntax and UDFs.
- If you cannot locate the fault or the call stack is incorrect, click the job name to go to the job details page and click the Commit Logs tab to view the job submission logs.
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
