For better scalability and stability, TrackStudio can be launched on several application servers grouped into a cluster. Load balancing makes it possible to distribute the load between servers in the cluster. 

A failover cluster is a set of servers that are configured so that if one server becomes unavailable, another server automatically takes over for the failed server and continues processing. 

TrackStudio uses a cache for data processing. The cache stores information about tasks and users that have been accessed and contains the results of database queries. When TrackStudio works within an application server cluster, it is important to synchronize the caches between cluster nodes. Once any object in the cache is changed, TrackStudio sends out notifications to TrackStudio instances running on other cluster nodes. Those notifications are used to update the objects in their caches.

1. Install TrackStudio on all cluster nodes. As TrackStudio uses broadcast messages to send notifications, the cluster nodes must be within one physical network. All instances must use the same version of TrackStudio Enterprise.
2. Edit the trackstudio.properties files on all nodes. Set trackstudio.cluster to yes and specify the same trackstudio.cluster.name for all cluster nodes. Set cluster node IP address if required.
3. Specify the name of the directory which will be used to store uploaded files. All instances must use the same directory in which to store uploads. You can use shared disk in Windows or NFS in UNIX.
4. Specify the name of the directory which will be used to store full text search index files. Each instance must have a local copy of index.
5. Configure database connections. All instances must use the same database.
6. Configure the other settings and launch TrackStudio on all cluster nodes. While loading, TrackStudio displays messages about active nodes in the cluster:

-------------------------------------------------------
GMS: address is TMK-12X3:4390
-------------------------------------------------------