Clustering
Description
Note: We have announced the deprecation of clustering. See our deprecation page for more information.
Clustering allows a single Terminalfour instance to be clustered over multiple application servers. All updates are automatically propagated to other servers within the cluster to ensure a consistent experience between all clustered servers.
- License keys can be tied to multiple servers.
- All configuration information is shared.
- All events within the system are serialized and propagated to all known servers in the cluster.
- Scheduled tasks will always take place on a single server instance within the cluster.
To configure Clustering, go to System administration > System settings > Clustering.
General options
Remote object port
The port number on which the remote objects bound in the registry receive calls. This defaults to a free port if not specified. Should be an unused port in the range 1025 - 65536.
Cluster nodes
There is no limit to the number of clustered nodes.
| Item | Description |
|---|---|
| Host | Sets the server hostname or IP address |
| Port | Defines the port number used by the application |
| Use as scheduled server | Sets the server to run all scheduled tasks |
| Use as index server | Sets the server as the index server |
Note: We advise that sticky nodes are enabled for clustered environments so users typically stay on the same server. This is required if MFA is enabled for local/LDAP users.