Skip to main content
Announcements
Jan 15, Trends 2025! Get expert guidance to thrive post-AI with After AI: REGISTER NOW

Qlik Talend Cloud: Job executed with Cloud Engine is failing with"code 137 and error Job stopped with errors or unable to run"

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
tomoya_suto
Support
Support

Qlik Talend Cloud: Job executed with Cloud Engine is failing with"code 137 and error Job stopped with errors or unable to run"

Last Update:

Nov 13, 2024 4:57:47 AM

Updated By:

Xiaodi_Shi

Created date:

Nov 13, 2024 3:05:11 AM

When using Talend Cloud Engine to run your jobs, if the following messages are list in your execution logs, it means there are memory issues occurring.

Execution {Execution number here} failed with code 137 and error Job stopped with errors or unable to run. (check the task execution logs for the error details)

 

Resolution

  • Try to monitor the resource consumption(CPU, Memory, Disk) on Cloud Engine and look at the amount of memory used for the current task to avoid/decrease useless memory consumption.

 

  • For Jobs that require more resources, consider using Talend Remote Engine(RE) or Talend Dynamic Engine (DE) as the target runtime.

 

Cause

It is a known issue for memory limitations in Talend Cloud Engine and error code 137 happens when system kills the process(out of memory issue)

The following system resource limitations are valid for Jobs running on Cloud Engines

  • vCPU: 2
  • Disk usage: 200GB
  • Memory usage: 8GB
  • Throughput: 225GB per hour

 

Related Content

Please find more details regarding Talend Cloud Engine here: Execution engines in Talend Cloud.

 

 

Environment

Labels (1)
Version history
Last update:
‎2024-11-13 04:57 AM
Updated by: