Executing Job tasks on a Remote Engine or a cluster - Cloud

Talend Remote Engine User Guide for Linux

Version
Cloud
Language
English
Operating system
Linux
Product
Talend Cloud
Module
Talend Remote Engine
Content
Design and Development
Installation and Upgrade
Last publication date
2024-02-23

By scheduling its run on a Remote Engine or cluster, your Job task will be executed in an on-premises secure runtime.

By default, you can run 3 different or identical tasks in parallel on a single Remote Engine. For further information about the related configuration, see Running tasks in parallel on a single Remote Engine.

Warning:
  • Current Remote Engine sub folders tree should be reserved for internal use.
    .
    ├── activemq-data
    ├── bin
    ├── data
    ├── deploy
    ├── esbrepo
    ├── etc
    ├── instances
    ├── lib
    ├── scripts
    ├── system
    └── TalendJobServersFiles
  • Job generated (permanent) files can be stored in any new directory outside of <RemoteEngineInstallationDirectory>.
  • Temporary files should be managed with the tCreateTemporaryFile component.

Procedure

  1. Open the Management page.
  2. Go to the Tasks tab.
  3. Select the task to run on the Remote Engine or cluster from the list.
    You can use the faceted search at the top of the page to filter the list for example by selecting the environment, workspace, and task type.
  4. On the task details page, click Edit next to Trigger.
  5. In the Edit task wizard, go to the Processing step.
  6. Select the Remote Engine or cluster on which you want to deploy the task from the Engine drop-down list.
  7. Optional: Select a run profile.
    You can choose a previously created run profile for the selected Remote Engine or cluster to set the JVM parameters for the task execution.
    This feature is supported from Remote Engine 2.9.1 onwards.
  8. Set the log level.

    Select the lowest log level to be taken into account.

    This feature is supported from Remote Engine 2.8.3 onwards.

    For example, if the log level is set to Warning, only logs flagged as Warning and Error will be displayed on the Task run log page.
  9. Optional: Select the Allow parallel run of this task option so that the task can be run in parallel when using a Remote Engine or a Remote Engine cluster.

    If you are using a Remote Engine to run identical tasks simultaneously, your Remote Engine must be v2.12.0 onwards.

    By default, you can run 3 different or identical tasks in parallel on a single Remote Engine. For further information about the related configuration, see Running tasks in parallel on a single Remote Engine.

    Before you disable this option, stop the task or wait for the end of the run. Otherwise, the parallel run is still allowed.

  10. Optional: If you have scheduled the execution on a single engine, you can run your Job as another user by entering their username in the Run as impersonated user field.
    This feature is supported only if the Remote Engine is installed on Unix or similar environments.
    For more information about user impersonation, see Configuring user impersonation for Talend Remote Engine.
  11. Optional: Set the task execution timeout by selecting one of the following options:
    • Custom then entering a value.

      The default value is 5 minutes and the minimum is 1.

    • Smart Timeout.

      For more information on smart timeout, see Enabling smart task timeout.

    Screenshot showing how to add task execution timeout.
  12. Click Continue.
  13. In the Schedule step, click the Add trigger icon then select the execution frequency and if necessary the trigger timeout.

    You can add one or more triggers to schedule your task or you can manually start the task without a trigger.

    Trigger timeout overrides task timeout. By default, the trigger timeout value is the same as the task timeout.

    For more information, see Scheduling Job tasks.
    Screenshot showing how to add trigger timeout.
  14. Click Save and close.

Results

Your task is ready to run on Talend Management Console.
Screenshot showing the task is ready to run.