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 2024-08-16 GMT+08:00

View PDF

What Can I Do If launcher-job Is Terminated by Yarn When a Flink Task Is Submitted?

Launcher-job is terminated by Yarn due to insufficient heap size when a Flink task is submitted on the management plane.

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

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.