Skip to main content

Talend High Availability

You can set up a cluster in your Talend system to provide high availability and failover features for task execution scheduling in Talend Administration Center. You do this by deploying multiple Job Conductors and Job execution servers on different machines.

Information noteNote: High availability in this context refers only to the scheduling of task executions. To enable high availability, see Setting up High Availability.
High availability diagram for TAC

To summarize:

  • Two application servers (Tomcat or JBoss) holding the Talend Administration Center Job Conductors and Virtual Servers, as well as two Talend CommandLine applications are installed (on different machines) and point to the same SVN/Git shared project.

    Availability-noteDeprecated
    Apache Subversion is deprecated from 7.3.1 R2021-08 release onwards

  • All instances of the application server are connected to the project administration database. Refer to your corresponding database vendor documentation for more information.

  • (optional) Talend Administration Center users are routed to the same active application instance, for example through an HTTP Proxy (switch). This feature is not provided by Talend and thus needs to be implemented separately.

  • When an execution server fails, the other execution servers can recover the interrupted tasks.

  • A shared storage is implemented to store and share between active instances all archives and logs generated during each Job execution, for example through a Network-Attached Storage (NAS). This feature is not provided by Talend and thus needs to be implemented separately.

For more information about the failover and the actions you can perform on a task when a server is unavailable, see Duplicating Tomcat and the TAC web application and Talend Administration Center User Guide.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!