Procedure
-
Duplicate this Tomcat instance on different servers, as many times
as needed.
Warning: Having different Talend Administration Center
Tomcat servers on the same OS instance are not supported when configuring high
availability.
Warning: Make sure that system clocks of databases and
servers are synchronized (the clocks must be within a second of each other). For
more information on time-sync services, refer to the Microsoft documentation about
SNTP, Windows Time Service tools, and Network Clocks.
-
Duplicate the org.talend.administrator Web
application to all Tomcat instances. Make sure that all Web application
configurations are identical.
-
For each Tomcat instance, open
configuration.properties
file in
the
<TalendAdministrationCenterInstallationDirectory>/apache-tomcat/webapps/org.talend.administrator/WEB-INF/classes
folder and set the value of node.identifier=
parameter.
Warning: Check that each Tomcat instance (or node) has a unique
identifier in the cluster.
-
Launch one Tomcat instance following the commands given in Deploying Talend Administration Center on Apache Tomcat.
-
Launch the other instances of Tomcat following the same
procedure.
Results
Fail-over will occur when one of the multiple execution servers fails
while in the midst of executing one or more tasks. When a server fails, the other
servers of the cluster detect the condition and identify the tasks in the database
that were in progress within the failed server. Any tasks marked for recovery will
be taken over by another server.
Note that the ranking of servers to be used for load balancing is based on
indicators, whose bounds (such as free disk space limits) and weight are defined in the
file: monitoring_client.properties which is located in
<ApplicationPath>\WEB-INF\lib\org.talend.monitoring.client-A.B.C.jar.
These values can be edited according to your needs. For more information, see Configuring the indicators which determine which server to be used for load balancing.
Important: One known minor issue related to the DST change might
prevent the failover to operate correctly. To work around this issue, restart Tomcat
after the time change. This should have no impact on executions.