Help Center/ MapReduce Service/ FAQs/ Job Management/ What Can I Do If launcher-job Is Terminated by Yarn When a Flink Task Is Submitted?
Updated on 2025-03-17 GMT+08:00
What Can I Do If launcher-job Is Terminated by Yarn When a Flink Task Is Submitted?
Symptom
Launcher-job is terminated by Yarn due to insufficient heap size when a Flink task is submitted on the management plane.
Solution
Increase the heap size of the launcher-job queue.
- Log in to the active OMS node as user omm.
- Change the value of job.launcher.resource.memory.mb in /opt/executor/webapps/executor/WEB-INF/classes/servicebroker.xml to 2048.
- Run the sh /opt/executor/bin/restart-executor.sh command to restart the executor process.
Parent topic: Job Management
What is your overall rating for this page?
0
1
2
3
4
5
6
7
8
9
10
Very dissatisfiedVery satisfied
Thank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.