Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Q&A with Qlik - Qlik Cloud Migration: Questions about migrating to Qlik Cloud? Catch the latest replay!
cancel
Showing results for 
Search instead for 
Did you mean: 
AravindSubbiah307
Contributor
Contributor

Talend Job automatically moves into Killed status

Hi, I'm using Talend Version: Patch_20220819_TPS-5325_v1-7.3.1. I have added my job to an execution plan which consists of 6 jobs. For couple of weeks, we are seeing some issue with the last job in execution plan. After 10 or 20 mins of execution, it gets into Killed status. no other user has killed it and there is no error mentioned in the log. Post the error, if we manually trigger the job, we are not seeing this error.

We have checked the CPU/Memory utilization in server it seems to be optimal. As well as the activity in DB is also normal. This job would get triggered around 8:45 AM and get killed around 9:08 AM.

What could be the cause for this issue? Has anyone ever faced similar issue and is there any solution for this.

0695b00000aDEEHAA4.png

Labels (5)
2 Replies
Anonymous
Not applicable

Hello @Aravind Subbiah​ ,

Could you please check if it's 'Reset task' for the task's 'On unavailable JobServer' settings in TAC?

if so, that's the cause. Every server in TAC has timeout in configuration. When you have “On Job Server Unavailable” - “Reset Task” it is by design after jobserver timeout kills task.

 

The possible solution is to change it to 'Wait'

Please refer to parameter 'On unavailable JobServer' in the below article

https://help.talend.com/r/en-US/7.3/administration-center-user-guide/adding-execution-task-to-artifact

 

Thanks

Aiming

 

AravindSubbiah307
Contributor
Contributor
Author

Hi @Aiming Chen​,

Thanks for the quick reply. Like you mentioned the job has been already setup with 'Wait' option for the 'On unavailable jobserver' parameter.

 

0695b00000aDEHGAA4.png