Talend High Availability - 7.3

Talend Installation Guide

Operating system
Subscription type
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 Activity Monitoring Console
Talend Administration Center
Talend Artifact Repository
Talend CommandLine
Talend Data Preparation
Talend Data Stewardship
Talend DQ Portal
Talend ESB
Talend Identity and Access Management
Talend Installer
Talend JobServer
Talend LogServer
Talend MDM Server
Talend MDM Web UI
Talend Repository Manager
Talend Runtime
Talend SAP RFC Server
Talend Studio
Installation and Upgrade
Last publication date
Available in...

Big Data Platform

Data Fabric

Data Management Platform

Data Services Platform

MDM Platform

Real-Time Big Data Platform

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.

Note: 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.

    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.