Job execution flowchart of release and cleanup - 8.0

Job execution: flowchart of release and cleanup

Talend Big Data
Talend Big Data Platform
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Real-Time Big Data Platform
Talend Administration Center
Last publication date

This section describes the Job execution workflow in Talend JobServer. It is a two-stage operation: first the release, then the actual cleanup.

Talend JobServer internally registers Job executions. An internal component called JobsManager maintains information about Jobs and their executions.

This information has an impact on the availability of:
  • the execution status,
  • an existing Job deployment (it may be cleaned up),
  • execution logs.

The following diagram shows what happens when a Job execution starts:

A counter called executionsCount is incremented. As soon as it exceeds the manageReleasingFrequency configurable value (which defaults to 50), the counter checks if the release of any Job execution is possible. executionsCount is a global count and is not restricted to the specific Job. If possible, the execution is released in the JobsManager.

When executionsCount exceeds manageReleasingFrequency, it is reset to 0. executionsCount counter is reset when Talend JobServer is restarted.